1605C5-25-R-00007 Attachment 5 - Part 7 - Technical Exhibit Index_Final.docx
DOCX document 1 MB Posted
- Attached to
- DOL BLS Electronic Data Collection (EDI) Center Operations Federal contract opportunity
- Solicitation number
- 1605C5-25-R-00007
About this file
This document is an RFP Attachment for the Department of Labor's Bureau of Labor Statistics (BLS) Electronic Data Interchange (EDI) Center Operations contract, specifically Attachment 5, which details technical exhibits and performance requirements. The solicitation seeks a contractor to process employment and wage data for large multi-establishment companies, with key performance objectives including processing Quarterly Census of Employment and Wages (QCEW) and Current Employment Statistics (CES) data within strict timeframes and quality standards.
The contract involves processing up to 625,000 incoming records monthly for QCEW and 325,000 for CES, with precise processing deadlines and quality metrics. Estimated labor hours include 25,760 hours for EDI Analyst 1, 16,560 hours for EDI Analyst 2, and 1,912 hours each for two EDI Computer Programmer positions, located in Chicago but with potential for remote work within the Continental United States. The technical exhibits provide detailed performance requirements, deliverables schedule, estimated workload data, glossary of terms, and data processing metrics across various modules and systems.
View the file
Other files for this federal contract opportunity
| File | Type | Posted |
|---|---|---|
| 1605C5-25-R-00007-0002_093025.docx | DOCX document | |
| Wage Determinations for EDI.xlsx | XLSX spreadsheet | |
| 1605C5-25-R-00007-0002_093025.pdf | ||
| 1605C5-25-R-00007-0002 Attachment 3 - Pricing Sheet EDI_Final.xlsx | XLSX spreadsheet | |
| 1605C5-25-R-00007 EDI_RFP Question and Answer_Final.xlsx | XLSX spreadsheet | |
| AMNT1 1605C525R00007.pdf | ||
| 1605C5-25-R-00007.pdf | ||
| 1605C5-25-R-00007 Attachment 1 - PPQ_Final.doc | DOC document | |
| 1605C5-25-R-00007 Attachment 3 - Pricing Sheet EDI_Final.xlsx | XLSX spreadsheet | |
| 1605C5-25-R-00007 Attachment 4 - RFP Question and Answer_Final.xlsx | XLSX spreadsheet | |
| 1605C5-25-R-00007 Attachment 6 - SMALL BUSINESS SUBCONTRACTING PLAN TEMPLATE_Final.xlsx | XLSX spreadsheet | |
| 1605C5-25-R-00007 Attachment 2 - BLS Confidentiality and Security_Final.docx | DOCX document |
Show all 12
On GovTribe
Work with this file on GovTribe
- Download the original file
- Contacts named in this file
- Similar government files
- Ask GovTribe AI about this file
Text version
RFP ATTACHMENT 5
1605C5-25-R-00007 EDI Center Operations
ATTACHMENT 5
Part 7 - Technical Exhibit Index Please refer to the individual tasks for the Performance Requirements Summary and Deliverables Schedule.
Technical Exhibit 1 – Performance Requirements Summary Technical Exhibit 2 – Deliverables Schedule Technical Exhibit 3 – Estimated Workload Data Technical Exhibit 4 – Glossaries Technical Exhibit 5 – EDI Data Appendix Technical Exhibit 6 – Low–Complexity Firm Notes Technical Exhibit 7 – Medium–Complexity Firm Notes Technical Exhibit 8 – High–Complexity Firm Notes Technical Exhibit 9 – CES Processing Checklist Technical Exhibit 10 – QCEW Processing Checklist Technical Exhibit 11 – Process Status Edit Checklist Technical Exhibit 12 – Failed Report Count Report Technical Exhibit 13 – CES Closing Date Calendar & QCEW Processing Calendar Technical Exhibit 14 – CES — Processing Review Checklist Technical Exhibit 15 – QCEW — Processing Review Checklist
Technical Exhibit 1 - Performance Requirements Summary Electronic Data Interchange Center Operations
| Performance Objective and PWS paragraph |
| Performance Standard |
| Acceptable Quality Level |
| Frequency of Inspection |
QCEW
(5.1)
| Validation that the correct reference month or quarter is processed |
| 100% |
| Monthly/Quarterly |
| MWR/RFEW quarterly data processing completed within designated week 10 export deliverable deadline |
| 100% |
| Quarterly |
| Initiation of MWR/RFEW processing within three business days |
| 100% |
| Quarterly |
| Process all incoming records (up to 625,000) |
| 100% |
| Monthly |
| Completion of MWR/RFEW quarterly data processing by designated week 10 QCEW export deliverable deadline |
| 100% |
| Quarterly |
| Completion of processing of financial firms by week five of the processing quarter |
| 100% |
| Quarterly |
| Completion of processing of all assigned incoming records within week five of the processing quarter |
| 50% |
| Quarterly |
| Completion of processing of all assigned incoming records within week eight of the processing quarter |
| 90% |
| Quarterly |
| Completion of processing of files with over 5,000 incoming records by week eight of the processing quarter |
| 100% |
| Quarterly |
| Completion of processing of assigned PEO files by week nine of the processing quarter |
| 100% |
| Quarterly |
| All MWR/RFEW processing work completed by ten-week deadline |
| 100% |
| Quarterly |
CES
(5.2)
| All usable files processed within two business days unless approved by the government |
| 100% |
| Monthly |
| All usable files received within two business days of CES Closing date processed by 4:00pm CT on that Closing date |
| 100% |
| Monthly |
| All usable files processed within two business days unless approved by the government |
| 100% |
| Monthly |
| All usable files received within two business days of CES Closing date processed by 4:00pm CT on that Closing date |
| 100% |
| Monthly |
| Process all incoming records (up to 325,000) |
| 100% |
| Monthly |
| Completion of post-processing subtasks within 10 business days following CES Closing date, unless otherwise specified by the government. |
| 100% |
| Monthly |
Questions and Firm Follow-Up (5.3)
| Clear and accurate preliminary responses to all BLS and state agency On-track questions within five business days |
| 100% |
| As needed |
| Responses to QCEW program office questions within five business days |
| 100% |
| As needed |
| Responses to CES program office questions within five business days |
| 100% |
| As needed |
Programming (5.4)
| Completion of all emergency programming tasks within deadlines established by GTM |
| 100% |
| As needed |
| Programming support completed within agreed upon time frames |
| 100% |
| As needed |
Technical Exhibit 2 - Deliverables Schedule
| Deliverable |
| Frequency |
| # of Copies |
| Medium/Format |
| Submit To |
| Staff Management Plan |
| Quarterly |
| 1 |
| PDF or similar |
| COR |
| Contractor Quality Control Plan |
| Draft with proposal. Final copy due within 90 days of contract award. |
| 1 |
| PDF or similar |
| COR |
| Telework Plan |
| Upon establishment and updated as needed |
| 1 |
| PDF or similar |
| COR |
| Phase-in Plan |
| Draft with proposal. Final copy due within 10 days of kick-off meeting. |
| 1 |
| PDF or similar |
| COR |
| Monthly Invoice |
| Monthly |
| 1 |
| PDF or similar |
| COR |
| Monthly report |
| Monthly within 10 days of CES 1st Closing. |
| 1 |
| PDF or similar |
| COR |
| Performance Period Funding |
| Eight weeks prior to the end of the performance period. |
| 1 |
| PDF, Excel, or similar. |
| COR |
| Phase-out |
| Draft 90 days prior to contract completion. Final 30 days prior to contract completion. The COR will provide any revisions required within 10 calendar days. |
| 1 |
| PDF or similar |
| COR |
Technical Exhibit 3 - Estimated Workload Data The estimates below apply only to the labor hours portion of the BPA. Management and supervision are not included below.
| Item Number |
| Labor Category |
| Estimated Hours (Base Period) |
| 1 |
| EDI Analyst 1 (Chicago) |
| 25,760.00 |
| 2 |
| EDI Analyst 2 (Chicago) |
| 16,560.00 |
| 3 |
| EDI Computer Programmer 1 (Chicago*) |
| 1,912.00 |
| 4 |
| EDI Computer Programmer 2 (Chicago*) |
| 1,912.00 |
*The EDI programmer positions can be filled remotely within the Continental United States.
Technical Exhibit 4 - Glossary
| Aggregation |
| Aggregation is a process by which establishments or units are grouped together within their corresponding FIPS, UI, EIN, and Addresses. Aggregation rules are provided by BLS. |
| All employees (AE) |
| Employment data refer to persons on establishment payrolls who worked or received pay for any part of the pay period that includes the 12th day of the month. |
| Benchmark |
| Work that is performed to ensure that Registry information for real report numbers in COMET matches the appropriate identifying information including UI number, RUN number, NAICS code, county code and town code in QCEW. |
| Bureau of Labor Statistics (BLS) |
| The Bureau of Labor Statistics of the U.S. Department of Labor is the principal Federal agency responsible for measuring labor market activity, working conditions, and price changes in the economy. Its mission is to collect, analyze, and disseminate essential economic information to support public and private decision-making. As an independent statistical agency, BLS serves its diverse user communities by providing products and services that are objective, timely, accurate, and relevant. |
| CATI |
| Computer Assisted Telephone Interviewing |
| Current Employment Statistics (CES) |
| CES is a monthly establishment employment survey of about 147,000 businesses and government agencies, representing approximately 634,000 individual worksites. |
| CES 1st Closing |
| The last day that data can be received to be included in the first preliminary estimate of CES data. |
| CES 2nd Closing |
| The last day that data can be received to be included in the first revision of CES data, released one month after the first preliminary estimate was released. |
| CES 3rd Closing |
| The last day that data can be received to be included in the final revision of CES data, released two months after the first preliminary estimate was released. |
| Closed Worksite Review (Module) |
| A module in SLED where processors resolve records previously closed in SLED but have returned in the current quarter. Closed worksite units are resolved by BLS procedures. |
| Coding of New Employment Sites (CONES) |
| Work that is performed to convert temporary report numbers to real report numbers. Temporary report numbers are assigned to new worksites until the worksite is processed in QCEW and given the appropriate identifying information including UI number, RUN number, NAICS code, county code and town code. Once QCEW information is available for the worksite, the temporary report number is replaced with a real report number. |
| COMET |
| Government developed system used to process monthly CES files received by the EDI Center. The SPIFF output file is the input file for COMET. When the processing of a firm file is complete, the data is sent to the government BLS office in Washington, DC. |
| Comment code |
| A two-digit code that explains data that failed edit & screening tests. |
| Commissions (paid at least once per month) |
| Commissions or bonuses that are paid at least once per month. If paid less frequently, then should not be collected. |
| Confidentiality breach |
| Any opportunity for, or actual instance of, an unauthorized individual accessing sensitive information. Examples of breaches may include mailing respondent surveys to an incorrect address, the loss or theft of a computing device, email or fax transmittals of sensitive information sent to an unintended recipient, or any unauthorized release. |
| Contracting Officer (CO) |
| A person with authority to enter into, administer, and or terminate contracts, and make related determinations and findings on behalf of the government. Note: The only individual who can legally bind the government. |
| Contracting Officer’s Representative (COR) |
| An employee of the U.S. Government appointed by the contracting officer to administer the contract. Such appointment shall be in writing and shall state the scope of authority and limitations. This individual has authority to provide technical direction to the contractor as long as that direction is within the scope of the contract, does not constitute a change, and has no funding implications. This individual does NOT have authority to change the terms and conditions of the contract. |
| Contractor |
| A supplier or vendor awarded a contract to provide specific supplies or services to the government. The term used in this contract refers to the prime. |
| Crosswalk Error (Module) |
| A module in SLED where processors resolve records that are new to SLED in the current quarter. Crosswalk errors are resolved by BLS procedures. |
| Data Edits (Module) |
| A module in SLED where there are checks for various errors on the firm file such as both name fields blank (Trade, Legal), incomplete physical location addresses, PO Box information in the Street Address field, and other errors. Detail edits are resolved by government procedures. |
| Defective Service |
| A service output that does not meet the standard of performance associated with the Performance Work Statement. |
| Delinquent |
| A respondent that is two or more months behind in reporting data. |
| Deliverable |
| Anything that can be physically delivered and may include non-manufactured things such as meeting minutes or reports. |
| EDB |
| Employee Database. Data provided by the Quarterly Census of Employment and Wages, against which the CES benchmarks its data. |
| EDI Server |
| The EDI Center has a virtual server housed and maintained in BLS headquarters in Washington, DC. |
| EDI Website |
| The EDI Center has a website developed and maintained by contract programmers in the EDI Center. The website contains all EDI developed systems, including SPIFF, as well as processing metrics and a report generating capacity. |
| Edit & screening |
| Test for determining if data are: 1) logically possible and 2) within expected ranges. CES runs edit & screening on data items for all collection methods to identify potentially inaccurate data for follow-up review. |
| Edit Errors |
| When a record fails a data validity check performed by COMET. An example would be having more Non-Supervisory employees than total employees at a worksite. Edit errors are resolved by government procedures. |
| EIN |
| Employer Identification Number. A nine digit number issued to an employer by the Internal Revenue Service. |
| Electronic Data Interchange (EDI) |
| The Electronic Data Interchange (EDI) Center in Chicago focuses on collecting information from large multi establishment companies. |
| Employment and Wage Edits (Module) |
| A module in SLED where data checks are performed on employment and wage data. The micro record values for each record in a firm are compared to the previous quarter's values. If the difference between the records is outside of parameters set by BLS in SLED, the record has an edit. An example would be having the total quarterly employee count at a worksite change by more the 25% from the previous quarter. Employment and wage edits are resolved by BLS procedures. |
| Employment Warnings (Module) |
| A module in SLED where a second set of data checks are performed on employment and wage data. The micro record values for each record in a firm are compared to the previous month's values. If the difference between the records is outside of parameters set by BLS in SLED, the record has an edit. An example would be having the total quarterly employee count at a worksite change by more the 25% from the previous month. Employment and wage edits are resolved by government procedures. |
| Equipment |
| A tangible item that is functionally complete for its intended purpose, durable, nonexpendable, and needed for the performance of a contract. Equipment is not intended for sale, and does not ordinarily lose its identity or become a component part of another article when put into use. Equipment does not include material, real property, special test equipment or special tooling. |
| Failed Reporter Count Report |
| Report generated in COMET showing the count of each edit and screening error for the selected firm. |
| Financial Firms |
| Any firm whose NAICS code begins with 52 or 53 are considered to be financial firms for EDI processing deadlines |
| Files |
| A collection of data organized in one electronic location. Within the EDI PWS context, files usually contain worksite, administrative, employment, and wage data about a specific firm over a specific time period. |
| FIPS |
| A two-digit numeric code used to designate a state. For example, Alabama is 01 and Illinois is 17. |
| Firm Notes |
| WORD document created for each firm processed by the EDI Center. The notes contain specific information for processing the firm file. |
| FTP Server |
| A server housed in Washington, DC that accepts firm files directly from a firm's computer. |
| Government Furnished Property |
| Property in the possession of, or directly acquired by, the government and subsequently furnished to the contractor for performance of a contract. Government-furnished property includes, but is not limited to, spares and property furnished for repair, maintenance, overhaul, or modification. Government-furnished property also includes contractor-acquired property if the contractor-acquired property is a deliverable under a cost contract when accepted by the government for continued use under the contract. |
| Government Property |
| All property owned or leased by the government. Government property includes both government-furnished property and contractor-acquired property. Government property includes material, equipment, special tooling, special test equipment, and real property. Government property does not include intellectual property and software. |
| Hours |
| These are the hours worked or for which pay was received during the pay period that includes the 12th of the month for all employees, production, construction, and nonsupervisory employees. Included are hours paid for holidays, for vacations, and for sick leave when pay is received directly from the firm. |
| Incoming Records |
| Each row of an incoming firm file should be considered one incoming record. |
| Key Personnel |
| Contractor personnel that are evaluated in a source selection process and that may be required to be used in the performance of a contract by the Key Personnel listed in the PWS. When key personnel are used as an evaluation factor in best value procurement, an offer can be rejected if it does not have a firm commitment from the persons that are listed in the proposal. The prime contractor is responsible for performance of all subcontractors. |
| Loss of Government Property |
| Unintended, unforeseen or accidental loss, damage, or destruction of government property that reduces the government’s expected economic benefits of the property. Loss of government property does not include occurrences such as purposeful destructive testing, obsolescence, normal wear and tear, or manufacturing defects. Loss of government property includes, but is not limited to:— Items that cannot be found after a reasonable search; Theft; Damage resulting in unexpected harm to property requiring repair to restore the item to usable condition; or Destruction resulting from incidents that render the item useless for its intended purpose or beyond economical repair. |
| Microdata |
| CES data items collected from respondents. |
| Missing Units (Module) |
| A module in SLED where processors resolve units that were processed in SLED the prior quarter but are missing in the current quarter. Missing units are resolved by BLS procedures. |
| Multiple Worksite Report (MWR) |
| The Multiple Worksite Report (MWR) form asks most multi-location employers to provide employment and wage data for all of their establishments covered under one Unemployment Insurance (UI) account in a state. Most multi-location employers with a total of 10 or more employees combined in their secondary locations are required or requested to complete the MWR. An employer's primary location is the location with the most employment in a state. All other locations within the state are secondary locations. |
| NAICS |
| The North American Industry Classification System (NAICS) is the standard used by Federal statistical agencies in classifying business establishments for the purpose of collecting, analyzing, and publishing statistical data related to the U.S. business economy. http://www.census.gov/eos/www/naics/ |
| New units (Module) |
| A module in SLED where processors input specific data for new units. New units are records that are new to SLED. An example would be a retailer opening a new store. New units are resolved by BLS procedures. |
| Non-Employment Non-Wage Edit (Module) |
| A module in SLED where processors resolve records with changes in all data except employment and wage items between the current quarter and previous quarter. An example would be having the address of a record change from the previous quarter. Non-employment and non-wage edits are resolved by BLS procedures. |
| Non-Personal Services |
| The personnel rendering the services are not subject, either by the contract’s terms or by the manner of its administration, to the supervision and control usually prevailing in relationships between the government and its employees. Non personal service contracts are authorized by the government in accordance with FAR 37.012, under general contracting authority, and do not require specific statutory authorization. |
| On-Track |
| An internal CES system for asking and responding to questions about collected data. |
| Overtime Hours (manufacturing only) |
| These are hours worked by all employees, production and related employees, and nonsupervisory employees in manufacturing for which overtime premiums were paid because the hours were in excess of the number of hours of either the straight-time workday or the workweek during the pay period that included the 12th of the month. Weekend and holiday hours are included only if overtime premiums were paid. Hours for which only shift differential, hazard, incentive, or other similar types of premiums were paid are excluded. |
| Payroll |
| Payroll refers to dollars paid for full- and part-time all employees, production, construction, and nonsupervisory employees who received pay for any part of the pay period that includes the 12th day of the month. The payroll is reported before deductions of any kind, such as those for old-age and unemployment insurance, group insurance, withholding tax, bonds, or union dues; also included is pay for overtime, tips, holidays, and vacation and for sick leave paid directly by the firm. Excluded from the payroll are bonuses (unless earned and paid regularly each pay period); other pay not earned in the pay period reported (such as retroactive pay); and the value of free rent, fuel, meals, or other payment in kind. Commissions are also included if paid at least monthly. |
| Physical Security |
| Actions that prevent the loss or damage of government property. |
| Point of Contact (POC) |
| A contact at a CES sample unit. Typically in the payroll department. A POC will, hopefully, become a CES respondent. |
| Post-aggregation Singles (Module) |
| A module in SLED where processors resolve records that are new to SLED in the current quarter. Missing units are resolved by BLS procedures. |
| Predecessor |
| A predecessor is an establishment and/or unit that previously reported under one UI Account number or Reporting Unit Number (RUN) that is now being reported under a different UI Account number/RUN number. The purpose of the predecessor UI/RUN is to identify establishments or units that might have changed ownership or UI Account reporting. Predecessor information is usually used in conjunction with successor information. |
| Predecessor / Successor (Module) |
| A module in SLED where processors document records that have a predecessor or successor UI/Run combination. The documentation consists of providing the predecessor and successor UI/Run combinations to the states. Predecessor-successor records are resolved by BLS procedures. |
| Pre-edit (Module) |
| A module in SLED where processors resolve records that are missing certain required data elements for SLED processing. Pre-edits are resolved by BLS procedures. |
| Problem Tickets |
| An internal EDI Center system for asking and responding to questions or issues related to the operations of the EDI systems like SPIFF and the EDI Website. |
| Production and Nonsupervisory Employees (PE) |
| This category includes working supervisors and all nonsupervisory employees (including group leaders and trainees) engaged in fabricating, processing, assembling, inspecting, receiving, storing, handling, packing, warehousing, shipping, trucking, hauling, maintenance, repair, janitorial, guard services, product development, auxiliary production for plant's own use (for example, power plant), recordkeeping, and other services closely associated with the above production operations. |
| Professional Employer Organization (PEO) client data processing (Module) |
| A module in SLED where processors can review a PEO’s client data records with errors that can be updated or corrected. This unique process only applies to PEO firms and only pertains to its client data information. SLED lists client data records with errors which can be updated or corrected by the analyst. PEO client data processing errors are resolved by BLS procedures. |
Professional Employer Organization
(PEO)
A professional employer organization (PEO) is a firm that provides a service under which an employer can outsource employee management tasks, such as employee benefits, payroll and workers' compensation, recruiting, risk/safety management, and training and development. The PEO does this by hiring a client company's employees, thus becoming their employer of record for tax purposes and insurance purposes. This practice is known as co-employment.
| Property |
| All tangible property, both real and personal. |
| Property Administrator |
| An authorized representative of the CO appointed in accordance with agency procedures, responsible for administering the contract requirements and obligations relating to government property in the possession of a contractor. |
| Property Records |
| Records created and maintained by the contractor in support of its stewardship responsibilities for the management of government property. |
| QCEW |
| The Quarterly Census of Employment and Wages (QCEW) program summarizes employment, wages and business identification information on a quarterly basis for over nine million establishments. |
| Quality Assurance (QA) |
| The government procedures to verify that services being performed by the contractor are performed according to acceptable standards. |
| Quality Control |
| All necessary measures taken by the contractor to assure that the quality of an end product or service shall meet contract requirements. |
| Registry |
| Business and respondent contact and location information. |
| Report (number) |
| A nine-digit number used to identify each worksite processed in COMET. The number corresponds to identifying information used for the worksite in the QCEW Program. |
| Report on Federal Employment and Wages (RFEW) |
| A report by which federal agencies report all of the locations the agency has in the state along with the employment and wages at each location. |
| Respondent |
| The person that provides data for a CES report(s). |
| RUN |
| Reporting Unit Number. The number assigned by the state to distinguish between records with the same UI account number. |
| Screening Errors |
| When a record fails a data check performed by COMET. The micro record values for each record in a firm are compared to the previous month's values. If the difference between the records is outside of parameters set by government in COMET, the record has an error. An example would be having the total employee count at a worksite change by more the 25% from the previous month. Screening errors are resolved by government procedures. |
| SINGLE RUN |
| A UI account Reporting Unit Number. The number assigned by the state to distinguish between records with the same UI account number. |
| Singles (Module) |
| A module in SLED where processors resolve records that are single records in a UI account with only one RUN. Resolution can lead to the UI account remaining as one RUN or being broken out into multiple RUNs. Single units are resolved by BLS procedures. |
| SLED |
| BLS developed system used to process quarterly QCEW files received by the EDI Center. The SPIFF output file is the input into SLED. When the processing of a firm file is complete, the data is sent to the specified state for further processing. |
| SPIFF |
| System for Processing Incoming Firm Files - An EDI developed system used to convert incoming firm files into a format acceptable by the processing system (COMET). SPIFF also does several data verification checks to confirm macro level accuracy and validity. |
| Subcontractor |
| One that enters into a contract with a prime contractor. The government does not have privity of contract with the subcontractor. |
| Successor |
| A successor is an establishment and/or unit that is now reporting under one UI Account number or Reporting Unit Number (RUN) that was previously reported under a different UI Account number/RUN number. The purpose of the successor UI/RUN is to identify whether a new unit is truly new or just an existing unit reporting under a different account. |
| TDE |
| Touchtone Data Entry |
| Temporary Report Number |
| A temporary report number is a report number that has a T in the 3rd position as opposed to a report number which is all numbers. Temporary report numbers are assigned to new worksites. The report number is temporary because it will be replaced with a real report number when identifying information is assigned to the worksite in the QCEW Program. Given the different timing of the CES and QCEW Programs, a real report number will not be available to replace the temporary report number until at least 6 months after the temporary report number is assigned. |
| Unemployment Insurance (UI) Account |
| UI account refers to a UI number. |
| Unemployment Insurance (UI) number |
| The Unemployment Insurance (UI) number assigned to the employer by the state. The ten digit number is for the account where an employer pays UI contributions. |
| Web |
| A reporting method where the respondent enters data into the CES web data collection tool. |
| Web Upload Server |
| A server housed in Washington, DC that allows firms to log on to a website to transmit their file. |
| Women Employees (WE) |
| All employees that are women. |
| Work Day |
| The number of hours per day the contractor provides services in accordance with the contract. |
| Work Week |
| Monday through Friday, unless specified otherwise. |
Technical Exhibit 5 - EDI Data Appendix Table 1: QCEW Firm Counts This table shows the total EDI processed QCEW firm counts per quarter, based on firm size. The columns represent the quarter that EDI collected data for QCEW, and the rows represent the number of records per firm. Each cell is a count of the number of firms that fit the corresponding row and column criteria. For example, the cell in the last row and first column shows that there were 11 QCEW firms reporting data to the EDI center with more than 10,000 records in the third quarter of 2019.
Table 2: QCEW Average Processing Time Per Firm (in hours) This table shows the average time it took to process a single QCEW firm each quarter, based on firm size. The columns represent the quarter that EDI collected data for QCEW, and the rows represent the number of records per firm. Each cell represents the average time (in hours) it took to process a firm that fit the corresponding row and column criteria. For example, the cell in the second row and third column shows that on average, in the first quarter of 2020, it took 8.47 hours to process a firm that had between 500 and 1000 records.
Table 3: QCEW Incoming Records Table This table shows the total number of incoming QCEW records received by EDI each quarter, per firm size. The columns represent the quarter that EDI collected data for QCEW, and the rows represent the number of records per firm. Each cell represents the total amount of incoming records EDI received for the corresponding firm size and time frame. For example, the cell in the first row and first column shows that in the third quarter of 2019, EDI received 24,691 incoming records from QCEW firms that each had less than 500 records.
Table 4: QCEW Average Incoming Records Table This table shows the historical change in number of incoming records from 2019 to 2023.
This table’s second column shows the average number of incoming QCEW records per quarter received by EDI each year. The third column shows the change from the previous year, and the final column is the change from the previous year as a percentage. For example, in 2022, on average, EDI received 746,102 incoming records per quarter. These 746,102 values is an increase from 2021’s quarterly incoming record average by 42,880 incoming records, or 5.7%.
*Through 2 quarters of 2023
Table 5: CES Firm Counts This table shows the total EDI processed CES firm counts per month, based on firm size. The columns represent the month that EDI collected data for CES, and the rows represent the number of records per firm. Each cell is a count of the number of firms that fit the corresponding row and column criteria. For example, the cell in the second row and first column shows that in December 2019, ten firms that each had between 500 and 1000 records submitted CES data to EDI.
Table 6: CES Average Processing Time Per Firm (in hours) This table shows the average time it took to process a single CES firm each month, based on firm size. The columns represent the month that EDI collected data for CES, and the rows represent the number of records per firm. Each cell represents the average time (in hours) it took to process a firm that fit the corresponding row and column criteria. For example, the cell in the fourth column and third row shows that on average, in December 2022, it took EDI 1.59 hours to process a firm that had between 1000 and 2999 records.
Table 7: CES Incoming Records This table shows the total number of incoming CES records received by EDI each month, per firm size. The columns represent the month that EDI collected data for CES, and the rows represent the number of records per firm. Each cell represents the total amount of incoming records EDI received for the corresponding firm size and time frame. For example, the cell in the third column and fifth row shows that in December 2021, EDI received 250,459 incoming records from firms that each had 10,000 or more records.
Technical Exhibit 6 - Low–Complexity Firm Notes
MWR FIRM NOTES
Name: Anycompany Inc Code: 1101271432 Contact: John Doe Email: john.doe@anycompany.com Phone: 999-999-9999 Website: http://www.anycompany.com/ Industry: PEO
Preprocessing Instructions: MWRPEO format
`File Format: PEO Mode of Receipt: MWRWEB Worksite Consolidation: No
1. In SPIFF, load the incoming raw file. Enter the Year and Qtr. Select PEO Consolidation Prep.
2. Rename the Consolidation Prep file XXyyqLOAD.txt.
3. Load to SLED.
Crosswalk Key is [RUN, WIC (Worksite ID), or RUD (Worksite Description)]:
· WIC
How to deal with new units (is there an aggregation scheme, how are units aggregated):
· There will be little to no aggregation. Normal PEO aggregation rules apply.
Statewide Workers (where are they reported, are statewide RUNs used):
· Delete any address fields where FIPS and STATE do not match. Be sure NOT to blank out RUD or WIC.
Industry Characteristics (What are the main NAICS codes, list by EIN and Legal Name/Trade Name if applicable):
· Many NAICS since firm is a PEO
Seasonal Changes (Are there seasonal wage/employment changes, when and for what type of unit do they take place)
· No seasonal changes.
Recurring issues/problems (these things happen every, or nearly every quarter):
· No issues.
Notes about current quarter (note the year/quarter, enter the most recent quarter at the top of box, default is “No issues.”):
· 2016 Q2: No issues
Things to consider for next quarter’s processing (same format as above):
· 2016 Q1: No issues
· 2016 Q2: Had several clients that had employment drop to zero in moth 2 or 3, but no termination date. Checked with respondent, John Doe, and he was able to provide term dates.
Technical Exhibit 7 - Medium–Complexity Firm Notes
Name: Big Firm Code: 0101100260 Contact: Jane Doe jane.doe@bigfirm.com phone 999-999-9999 (file sender) John Doe, john.doe@bigfirm.com (Back Up) Website: bigfirm.com Industry: Banking and Finance Preprocessing Instructions:
File Format: 350Y2K Mode of Receipt: FTP Worksite Consolidation: YES
1. Use 3rd month's CES file that arrives in MWR format.
2. Right click on the text file, open with TexPad. Visually verify file format and field content.
3. Save file as XXXyyqraw.txt.
4. Run SAS pre-processing program in F\Big Firm\MWR, entitle BigFirm_preproc.sas. This program will aggregate records based on fips, ein and worksite identification code. The program will also blank out address fields of "work at home" employees (where worksite like "WORK AT HOME"). Files save out are: bfc YYQ sas.txt and bfc YYQ sas.xls.
5. In SPIFF, load bfcYYQ SAS.txt. Select "identify average employment <1 and update WIC to STATWIDE."
6. Copy the Load text, Load excel and Raw excel files from N:\Attachments to firm folder.
7. Rename the 0101100260 Load file to BCyyqLOAD.txt.
8. Load to SLED.
Crosswalk Key is [RUN, BLS Only (aka Worksite ID), or RUD (aka Worksite Description)]:
· RUD
How to deal with new units (is there an aggregation scheme, how are units aggregated):
· Aggregate to the statewide units.
Statewide Workers (where are they reported, are statewide RUNs used):
· There are statewide workers. They can be identified by the RUD.
Industry Characteristics (What are the main NAICS codes, list by EIN and Legal Name/Trade Name if applicable):
· The best way is to refer to the EDB by Fip and EIN.
· Some of the NAICS by EIN are:
* 111111111, Big Firm Investment Services-523930
* 888888888, Big Firm Bank - 522110
* 999999999, Big Firm Mortgages - 522292
* 000000000, Big Firm Securities - 523110
Seasonal Changes (Are there seasonal wage/employment changes, when and for what type of unit do they take place)
· 1st quarter bonuses can be very large.
Recurring issues/problems (these things happen every, or nearly every quarter):
· File has been late for several quarters. Carefully review employment. Watch for negative wages.
Notes about current quarter (note the year/quarter, enter the most recent quarter at the top of box, default is “No issues.”):
· 14/2: Wages returned to normal after 1st QTR Bonuses.
· 15/1: Large bonuses were paid out. Also, Big Firm is in the process of closing about 30 branches over the next two years.
· 15/2: No issues
· 15/3: No issues
· 15/4: No issues
· 16/1: Bonuses
· 16/2: Wage returns to normal after bonuses.
Things to consider for next quarter's processing (same format)
· Be sure to do research since Big Firm is in the process of closing abut 30 stores over the next two years. Also, wages will be returning back to normal after Quarter 1 2015 bonuses.
· Big Firm plans to move some New York employees to New Jersey-Watch for transfers.
· Big Firm plans to open a new operations center in Wilmington, DE
Technical Exhibit 8 - High–Complexity Firm Notes
CES Firm Notes
Firm Name: Big Thing Somewhere Firm Code: 0101110270 Description: Big Thing Somewhere Corp. is a U.S. chain of big thing stores Website: www.bigthingzzz.com Contact: John Smith E-mail: jsmith@somewhere.com Preprocessing Instructions:
· File arrives via email from firm contact as an excel file (a 2nd file comes along entitled Closed Stores which is a list of all the closed or reopening locations in the country. Save this file to the firm folder as this will help with processing).
· Locate state alpha in CMT column. This indicates a duplicate record.
· Check the statewide units marked with FIELD and ADMIN for duplicates.
· Add smaller unit to larger, then delete line with CMT value.
· There are a couple of guidelines pertaining to Zero Employment and Wages on the raw file:
1. If AE and WAGES are blank, delete record(s).
2. If AE field is blank but WAGES are reported (no negative values), keep record and zero fill-in both the AE and the WW columns.
3. If WAGES are Negative values, delete record(s).
4. IF AE field is reporting employment, but WAGES are blank, keep record(s) and zero fill-in WW column.
5. IF AE field is reporting AE, and WAGES are present and WW is blank, than zero fill-in WW column
6. IMPORTANT: Keep WAGES on RAW File only for the months of: JANUARY, APRIL, JULY, & OCTOBER. You must delete all other month’s wages, otherwise COMET will not have the correct wages when the file is extracted for QCEW processing.
7. Make sure the MONTH column has a two-digit number. (i.e. 02, 03, 04, 05, etc.)
8. Delete the following columns: PC, NAME, RUN, DID, SID, PW, PR, HR, LP, COM, CLP, OT and the CMT column.
9. Adjust column widths:
EIN: 9 UI: 10 WID: 10 STA: 35 CITY: 30 ST: 2 ZIP: 5 MO: 2 YR: 4 AE: 7 WW: 7
WAGES: 10 (only for JAN, APRIL, JULY and OCT)
10. Delete Header row.
· Save file as “ZZZMMYYraw.xlsx”.
· Save file as “ZZZMMYYraw.prn” (space delimited). Open the raw.prn with Textpad and save out again as “ZZZMMYYraw.txt”.
· Close the PRN file in Excel and when prompted click no to save (it has already been saved)
· Run raw file through SPIFF.
· Rename firmcodemmyyLOAD as “ZZZMMYYload.txt”.
· The load.txt file is now ready for COMET processing.
Edits and screening (are there usually a lot of errors, what kind are they, what are typical comment codes:
· Edit and screening errors average about 50-200 per month and are usually more business/less business.
· For changes in WW errors please use CC#64.
· During Holiday season, use CC#01/02 unless you specifically know that it is CC#03/04, more business or less business.
· Firm also send a list of stores closed/reopening with New store number, make sure you save these files, they come in handy when doing QCEW
· If you need any valid street addresses, use the website store locator (by zip code) to find store number and edit the address in COMET.
· Please make sure to confirm with the location in question; Store management is more than happy to let you know if they have been closed down due to remodeling/restocking/retooling, etc.
Seasonal Changes (Are there seasonal employment changes, when and for what type of units do they take place)
· Seasonal changes are possible since the firm is a retail industry. These changes likely occur during major holidays.
Recurring issues/problems (these things happen every or nearly every month):
· There are recurring duplicates that show up in COMET and need to be fixed before processing load file.
· ADD together the AE, WW and WAGES (if required) to the record with the SAME EIN, RUD, & Address
Notes about current month (note the year/month, enter the most recent month at the top of box):
· 11/2015 - 03/2016: No issues, fixed duplicates.
Things to consider for next month's processing (same format as above)
· 04/2016: Fix duplicate import errors before SPIFF verification. Follow directions in pre-processing section.
Technical Exhibit 9 - CES Processing Checklist
FIRM:
DATE:
INITIALS CONFIRM CHECKLIST
STEPS READ & APPLIED
I. FIRST, CREATE A PROCESSING STATUS for Month/Year in EDIWeb. Key the accurate arrival date.
II. Perform firm-specific, Preprocessing steps. READ firm notes. If needed, consult previous analyst, BLS Team POC or Supervisor.
QA Pre-Processing
Firm Notes followed
Autostan file used if instructed by notes
Data Verification
***** Compares current load file vs Last month's load file.*****
I. Open EDIWeb
Click EDI Login, Enter Login informaton
Select CES ¿ Select Firm ¿ Under SPIFF tab select Create CES Files.
Note: DOUBLE CHECK for the correct MONTH & YEAR.
DOUBLE CHECK Mapping & Conditions before creating CES Files.
If anything needs to be changed OR looks unusual, consult with BLS Team POC or Supervisor.
Browse to select your CURRENT month's RAW.TXT file.
Set the current year and the current month and click Load.
The system will take you through various steps.
The files SPIFF creates during the process are located in N:\Attachments.
The names of the SPIFF created files have the numerical FIRM CODE as a prefix on the filenames
Copy these files from N:\Attachments to your firm folder in E: or F: and rename to xxxMMYYraw.xls, xxxMMYYload.txt and xxxMMYYload.xls (xxx is firm abbreviation, MMYY is 2 digit month and 2 digit year)
Use Autostan file only if mentioned in the firm notes.
II. System displays a DATA VERIFICATION report.
If the verification is successful (AE & RecCount Change less than 5%), Go to Step V
If the verification fails (AE & RecCount Change greater than 5%), go to Step III.
III. Investigate the reason for verification failure. BLS requires a reason for change prior to verification approval.
Was Pre-processing done correctly?
Was correct previous month file selected?
Does incoming show correct month & year?
2. The DATA...What's missing? What's new? Are there records missing employment?
Is this following normal business trends for this firm? Enter reason in EDI WEB notes section. (Check firm notes, Previous months verifications)
If no reason is found, click Stop File Creation Process.
If reason is received enter comment in the notes section and click Send Data Verification Approval Process.
Contact firm if necessary and request new data or an answer to explain the over-the-month change.
IV. A VERIFICATION APPROVAL email from BLS will signal readiness to continue.
Go to EDI WEB¿ CES¿Select firm¿ Under Workload tab select Processing Status¿
Select Current MONTH ¿ Click "Check Approval Received"
V. Copy the following data.
1. Record your Incoming Records and Total Employment
Incoming Records:
Total Employment:
2. The system will then create your CES files located in N:\Attachments.
COMET
I. Go to COMET
II. Enter your USER ID and PASSWORD. Your user ID is lastname.firstname (same as your BLS email).
III. Click on "Check Firm Out" to Check out firm needed for processing.
1. Select the firm needed for processing.
2. Make sure you have selected ALL FIPS.
3. Click Check Out at the bottom of your screen.
IV. Go to Data Processing. Select the load file to be imported, After selecting load file click Validate.
QA COMET Processing
Import errors properly resolved
V. The system will give you the # of import errors. Copy this number down. If there are none go to step VI
1. Save out Excel file for Import Errors as xxxMMYYImpErrors.xlsx
2. Resolve Import Errors outside of COMET, Click No At "Would you like to continue importing the file?"
3. Resolve import errors, Re-import the file.
VI. Copy down Total Records in File.
1.Click Yes, when ready to import the file.
QA COMET Processing
New units processed correctly
Report numbers assigned appropriately in the past
VII. The system will provide new units & delinquents.
1. Copy the # of new Units
2. Save out Excel file for New Unit as xxxMMYYNew.xlsx
3. Save out Excel file for Delinquents as xxxMMYYDelinquents.xlsx
4. Click Yes, After saving New & Delinquents Reports.
VIII. The system will provide Subdata Results.
1. Copy the # of Error Records
2. Save out Excel file for Batch Edits Subdata Report as xxxMMYYSubdata.xlsx
3. Click Yes, After Saving Subdata Report.
IX. The system will ask to Resolve New Units before Aggregation process.
1. Sort the window based on the Notes
2. System has auto default sort by : FIPS, EIN, CITY, ADDRESS.
3. CES Num Colors, A. BLUE = SINGLE
B. RED = PARENT
C. WHITE = HAVE A PARENT
4. Until all the New units are resolved you will not be able to move to next step.
5. After resolving New units, Click on Aggregate.
X. The system will provide Aggregate results.
1. Copy the # of Aggregated Records.
2. Click Yes.
XI. The system will ask for Batch Edit CES Data.
1. Please select EXCLUDE RC 90.
2. Click YES, After Selecting EXCLUDE RC 90.
QA COMET Processing
Edit & Screening errors coded properly
Errors from previous months coded properly
Additional Batch Edit Test verified
XII. The system will provide Edit & Screening Errors
Copy the # of Edit & Screening Errors.
A. PrintScreen the Batch Edit CES Data Screen into a Word Doc.
B. Save it to firm folder as xxxMMYYBatchEdits.docx
C. Review the results shown for Additional Batch Edit CES Data
D. If all error counts are ZERO, Go to Step 2.
a. If any of the edits have 1 or more errors, see your BLS team lead or supervisor.
b. Copy the # of Additional Batch Edit CES Data Result:
Save out Excel file for Edit & Screening as xxxMMYYEditScreen.xlsx
3. Click YES, To Resolve Edit Errors, Screening Errors & Subdata Errors.
4. Before resolving any errors, Save out Excel file for Failed Report Counts.
5. Click Reports, then Click Failed rept Counts save Excel as xxxMMYYFailedCounts.xlsx
6. To go back to Resolving Errors, Click Data Processing & than Edit & Screening.
7. You can perform a sort by clicking on RC(Micro) tab, "11" (Edit Error) or a "12" (Screening Error)
8. Either selection will bring up those errors after clicking the "Filter" button.
9. Once the errors appear, go to the Micro Data Screen.
You'll see current micro data and historical data. Place your cursor in the blue field to see what the error is.
You also can refer to the edit & Screening report to see the error and four months of micro data.
12. Once you've coded all or some of your errors, then click on save.
13. If you have any uncoded edits, they will not export. They are called "WITHHELD" units.
14. Copy the # of WITHHELD units.
15. All WITHHELD Records must be coded before processing the new month.
XIII. Check the firm back into server.
1. Click Check In.
2. Select the firm you wish to Check In OR Undo Checkout.
Check In - when you are done processing and want the data to be exported.
Undo Checkout - when you do not want to save your work.
3. Click Check In OR Undo Checkout.
XIV. Exports will be conducted centrally by a government administrator.
QA Post-Processing
CES processing checklist complete
Data metrics keyed in EDI Web
Firm notes current and updated
Electronic File maintenance completed
Post Processing
I. Enter the CES processing information into EDI WEB. Enter any unusual issues in the notes section. Remember to save your entries.
II. DO NOT ENTER any data for Date Exported Or Exported Records
III. Exports will be conducted centrally by a BLS Administrator.
IV. Update the firm's Processing Notes with relevant detail.
V. Delete extra month's from firm folder.
VI. Return to page 1 of this CHECKLIST to initial, indicating compliance with all CES Processing Checklist steps.
File Naming Conventions
I. Incoming original file : Do not change the incoming name.
II. Formatted Original File: xxxMMYYRaw.txt
III. Load File: xxxMMYYLoad.txt
IV. Load XLS: xxxMMYYLoad.xls
V. Import Errors: xxxMMYYImpErrors.xlsx
VI. New Records : xxxMMYYNew.xlsx
VII. Delinquent Units: xxxMMYYDelinquents.xlsx
VIII.Batch Edit Subdata Reports: xxxMMYYSubdata.xlsx
IX. Additional Batch Edit CES Data: xxxMMYYBatchEdits.docx
X.Batch Edit CESData Report: xxxMMYYEditScreen.xlsx
XI. Failed Report Counts: xxxMMYYFailedCounts.xlsx
Technical Exhibit 10 - QCEW Processing Checklist
Firm Name: _________________________________________ YR/QTR: ______
Create a processing status for the ref yr/qtr in EDI WEB. Enter Arrival date.
AT ANY POINT IN PROCESSING IF IT DOESN'T LOOK RIGHT, ASK A QUESTION!!!
QA Pre-Processing
Firm Notes followed
Consolidation Prep used if instructed by notes
Pre-Processing Outside of SLED : Any firm-specific steps to make the file useable or improved
Review Firm Notes in E: and F: See previous processor, ORI Supervisor or Trainer if help is needed.
Pre-Processing Outside of SLED : EDI WEB/SPIFF
On the internet, go to EDI WEB. From the EDI WEB home page, login, then select MWR --> Select Firm--> Under SPIFF tab select Create QCEW Files. The files SPIFF creates during the process are located in N:\Attachments. The names of the SPIFF created files have the numerical FIRM CODE as a prefix on the filenames. Copy these files from N:\Attachments to your firm folder in E: or F:. Rename to XXXYRQload and XXXYRQraw.txt (XXX is firm abbreviation).
Data Verification --Compares current load file vs last quarter's load file
Load file -- System displays a data verification report.
- If the verification is successful (OTQ change less than 5%), write down the number of incoming records column below.
- If the verification fails (OTQ change greater than 5%), the process will stop. The system will generate an email to BLS for approval. Follow instructions below.
Investigate the reason for verification failure. BLS requires a reason for change prior to verification approval.
- Was pre-processing done correctly?
- What data are missing? What's new?
- Is this following normal business trends for this firm?
- Firm notes and previous QTRs verifications checked?
**** Contact firm, if necessary and request new data or an answer for the big over-the-quarter change.
****Enter reason in EDI WEB notes section.
- Continue when you have received Verification Approval Email from BLS.
- Go to EDI WEB--> MWR-->Select firm--> Under Workload tab select Processing Status-->
- Select Current QTR -->Click "Check Approval Received"
The system will create and save the MWR files to N:\Attachments.
- Record the number of incoming records.
- System will display EINs and Names to be uploaded.
- If there are invalid data, research and reload raw.txt after corrections.
Copy load file to the firm's folder on the SLED (Y drive).
After data verification, LOAD file into SLED to see number of Crosswalk errors. A number of problems could be “discovered” earlier in the processing cycle when this step is followed.
In Step 38 of this Checklist you will be asked to update firm notes. Take notes as you process and this step will be easier.
All documentation must be electronic
An electronic version of the processing checklist and database checklist must be saved
SLED Processing
1. Go…
This is the start of the file's text. The full file is on GovTribe.
File details come from the government source that posted it. Updated .