Attachment_5_-_Sample_Task_Order_Track_1.doc

PROCUREMENT SENSITIVE – LIMITED DISTRIBUTION WITHIN DOL ONLY

Sample task order For Track 1 (Systems Engineering) U.S. Department of labor 200 Constitution Avenue NW, Washington, DC Table of Contents

21.0 Background

22.0 Objective

33.0 Scope of Work

44.0 Requirements

85.0 Period of Performance

86.0 Place of Performance

87.0 Schedule/Milestones For Sample Task

98.0 Acceptance Criteria

99.0 Required resources For Sample Task

1010.0 Evaluation Criteria For Sample Task

1011.0 Security Requirements

1.0 Background The Department of Labor (DOL) has recently laid out its vision for IT modernization and consolidation. Towards this goal, DOL OASAM-OCIO has published the Information Resource Management (IRM) strategic plan available at http://www.dol.gov/oasam/ocio/DOL-IRM-SP.pdf . Key elements of the DOL IRM plan include IT Modernization infrastructure integration, data center consolidation initiative (DCCI), shared services across agencies, unified communications, integrated enterprise services such as Cloud E-Mail, Collaboration, and Mobility, and strategic data management in support of its strategic plan to unify and redesign its data delivery platform and in support of the Federal Digital Government Strategy (https://www.whitehouse.gov/sites/default/files/omb/egov/digital-government/digital-government.html ). Although DOL is in the process of consolidating IT infrastructure across its sub agencies, there remains a wide variety of database platforms (e.g., Oracle, SQL, DB2, Postgress), case management systems (e.g., Drupal, SharePoint, Salesforce), and software development platforms (e.g., Cold Fusion, Rational, Java). The divergent database platforms, to choose just one example, and the lack of a cohesive data integration strategy has hindered DOL’s ability to share key labor law enforcement data that would benefit DOL’s enforcement agencies in meeting their missions. Through the IT Modernization initiative, OASAM-OCIO envisions a centralized data warehouse that will source the data from various enforcement agency case management systems and integrate the data into a unified data architecture. Over time other data sources will be added to enrich the data warehouse and enable a corporate level view of the regulated entities that are subject to the DOL enforcement actions. While this platform will result in changes to our client delivery tools the scope of this initiative is much broader than just technology and delivery tools. It incorporates all aspects of our business model including; administrative processes and tools, business processes, data collection, data warehousing, data management and employee productivity and citizen-client engagement. Historically, the IT organization at DOL has been federated in that many of the sub-agencies at DOL (e.g., OSHA, Wage and Hour Division, Employment and Training Administration, etc.) have their own IT organization and budget. The initial benefit of this structure was to give DOL’s agencies the autonomy (from an IT perspective) to make IT investments and strategy decisions that were in the best interest of the specific sub-agency. However, the drawback of this structure was that it resulted in duplicative infrastructure and tools, and systems that were often not interoperable or not based on uniform standards-based solutions. The technical challenges in dealing with such disconnected solutions are most evident when DOL undertook an enterprise-wide IT modernization initiative (e.g., Windows desktop upgrades, cloud e-mail migrations, etc.) and had to develop workaround strategies to overcome the variety of technology environments in use at DOL.

2.0 Objective We envision multiple DOL tool, application and data delivery options all managed through a unified data Delivery Platform that is separate and distinct from our existing and legacy application platforms. For example, DOL has several agencies that enforce a variety of labor laws; OSHA, Wage and Hour Division, and Office of Federal Contract Compliance Programs (OFCCP). Conceptually, each of these agencies has a similar mission in that they audit/inspect employers to determine their compliance with federal safety and labor laws. By centralizing corporate labor law violations into an enforcement data warehouse, DOL can gain a more comprehensive view of repeat violators and trends. This will allow DOL to focus their enforcement efforts and maximize resources. This will allow us to pursue many different options for delivering data and insights to our employees and the US workforce. Enabling Strategic Data Management capabilities includes: data modeling, repository, warehouse, analytics, and digital asset / content management. This will be enabled through our new Enterprise Data Management Platform (EDMP) project. The primary elements of EDMP are a Two-Tier Strategic design and implementation:

1. Tier 1- Enterprise Data Warehouse (EDW) including Data Modeling, Collection, Cleansing and Storage

2. Tier 2- Enterprise Content Management and Analytics (ECMA): Data Marts and tools for Data Analysis and Information Distribution DOL anticipates that its platform will simplify operations to increase cost efficiency and improve data-driven decision making and employee productivity.

3.0 Scope of Work One of the core elements of our plans and strategy to modernize data delivery and data-driven digital service is our Enterprise Data Warehouse (EDW) which will enhance our ability to deliver relevant data in a timely manner via a DOL portal or shared services. The scope of work for the EDMP Project includes all planning, execution and implementation for Tier 1 of our data-driven digital delivery program- Enterprise Data Warehouse – Data Modeling, Collection, Cleansing and Storage.

The Contractor shall be responsible for the design, development, validation and testing of the new EDW based on feedback to be provided by the DOL technical COR.

Each stage of the project will require approval from DOL management before moving on to the next stage. The Contractor must ensure it has adequate resources for designing, building, testing, and implementing the new warehouse. Specific deliverables and milestones will be listed in the Task Requirements and Schedules and Milestones sections of this PWS.

Not included in the scope of work for this project is any work on the Tier 2 of the program- Enterprise Content Management and Analytics (ECMA): Data Marts and tools for Data Analysis and Information Distribution.

The contractor shall provide project management support for the key development activities of the project as defined in the scope above. It is anticipated that the engineering services needs for completing this sample task includes some or all of the following Track 1 Systems Engineering disciplines as specified in the IDIQ Performance Work Statement:

· Information and Data Engineering

· Systems Integration Engineering

· Software Engineering

· Enterprise Solutions Engineering

· Baseline Assessment

· Project Management of Engineering Efforts

The combination of engineering disciplines and corresponding labor hours for each discipline should be determined by the contractor based on their understanding and expertise in the task requirements. The contractor shall review the Project Charter for overall direction and insure that project execution occurs in accordance with DOL’s overall strategic plan.

The contractor shall conduct interviews with staff to determine specific requirements for execution of tasks associated with the scope of this project. The contractor shall work with the program lead to develop a comprehensive project plan (roadmap) that identifies the tasks, defines project staff roles/responsibilities, and provides a timeline for completion of tasks.

The contractor shall be responsible for providing on-going evaluation of project work, quality, and timeliness for completion of projects.

4.0 Requirements

4.1 Introduction:

Upon successful design and deployment of Enterprise Data Management Platform (EDMP) project, DOL employees will be able to capture audio, video, images, and location data, and integrate these digital assets with various business systems: case management, web-sites, distance learning, records management; as well as in digital courtrooms – to achieve greater efficiency in mission execution, and transition DOL to 21st century government. Occupational Safety and Health Administration (OSHA) inspectors will be able to deliver targeted content, including videos, photos, and audio on construction safety materials to workers.

Strategic Data Management capabilities including data modeling, repository, warehouse and analytics, and digital asset management, and integration with geospatial information that will allow DOL to collect, share and multi-purpose data, including audio, video, and images across DOL agencies. For example, images or video collected by investigators could be integrated with case files, shared with counsel for use in the digital courtroom or used on web-sites and online training sessions. The capability will vastly improve access to Unemployment Insurance (UI) program workload, financial and performance data used for program oversight and evaluation of the performance of states' UI program operations by Office of Unemployment Insurance (OUI) and Employment and Training Administration’s (ETA) Regional Offices. A common repository and warehouse will not only help OUI but facilitate sharing of data within ETA and across DOL as well. Additionally, the easy access to data and the analytics capability will help staff to effectively develop analytical reports and charts as well as translate data into meaningful information that can be used by management to assess the performance and take informed corrective actions.

Towards this goal of Strategic Data Management, the Enterprise Data Warehouse (EDW) is a critical element within the EDMP that needs to be successfully design and implemented. In this task involving EDW design, development, implementation and validation, the contractor must be able to work collaboratively with internal and external agencies to identify data sources, develop the ETL processes necessary to consolidate the data into a centralized data warehouse according to a unified data model, make the data consumable by other 3rd party applications via flexible and current web services technology.

Data providers- DOL has approximately 3-4 agencies which are data providers to the proposed warehouse. In total, DOL estimates that a total of approximately 3000 employees across these agencies who may transmit data source information to the warehouse, and approximately 3000 end-users of the EDMP.

The initial agency partners for EDMP will be:

· Occupational Safety and Health Administration (OSHA): http://www.osha.gov/index.html

· Mine Safety and Health Administration (MSHA): http://www.msha.gov/

· Wage and Hour Division: http://www.dol.gov/whd/

· Employment and Training Administration: http://www.doleta.gov/ Data Formats: The existing data formats that the EDW should be capable of handling are: flat text files, csv, xls , txt, xml, JSON, and html, file formats, images in JPEG, GIF format, audio files in MP3, WAV, WMA, AIFF, M4A, and AAC and videos in MPEG-1, MPEG-2, and MPEG-4, 3GPP, AVI, WMV, FLV, and MOV format Volume -The data warehouse size is approximately 50 TB. The customer base for future data marts developed off this data warehouse spans approximately 9,000 users.

Frequency- The data warehouse will need to render and stage data at a frequency of 24 hours. The publication to standardized warehouse tables can happen once daily.

Hardware & Software Technology Stack- Contractor shall provide a detailed Cost Benefit Analysis of hardware and technology stack needed to create the proposed solution. DOL is open to either traditional licensed or open source s/w or a mix of both to create a unique scalable solution.

Components to the solution must include:

The environment, OS to host the data warehouse and ETL repository

Staging site : ftps/ EDX etc for data providers to host their data

Network and Security configuration- EDMZ/ internal and external security protocol

The ETL tool to collect, cleanse and consolidate the data.

The contractor must be able to architect an EDW system architecture that complies with all commonly employed necessary security controls and specifications, such as, NIST Special Publication 800-53 (http://csrc.nist.gov/groups/SMA/fisma/controls.html ), FIPS 200 (http://csrc.nist.gov/publications/fips/fips200/FIPS-200-final-march.pdf ), and FIPS 199 (http://csrc.nist.gov/publications/fips/fips199/FIPS-PUB-199-final.pdf ).

The contractor must be able to design and implement a data warehousing architecture that appropriately addresses the DOL Computer Security Handbook confidentiality, integrity, and availability requirements of the system.

The contractor must be able to develop user interfaces that meet Section 508 accessibility requirements.

The contractor should evaluate cloud-based solutions as a design option for the EDW (i.e., Infrastructure As A Service, Platform As A Service, and Software As a Service).

As part of the EDMP project the Contractor shall be responsible for performing tasks throughout various stages of this project. The following is a list of these tasks which will result in the successful completion of this project:

The Contractor shall provide the following:

4.2 Kickoff:

· Review Project Charter jointly with the DOL team.

· Contractor shall create and present detailed project plan including schedule, WBS, design documents, technology stack, dimension and fact models Use Cases, testing plan and implementation plan.

· Formalize the Monthly Status report format- Should include Functional activity progress and Cost Performance status.

· Contractor shall present project plan to DOL for review and approval. This should include

· A summary of work performed by task functional area for the reporting period

· Milestones and tasks

· Resource type and staff allocation

· Estimated Billing hours

4.3 Design Phase:

· Assist with DOL with defining and gathering requirements and establish data providers, data formats, prime challenges, warehouse usage and key metrics. The existing data formats that the EDW should be capable of handling are: flat text files, csv, xls , txt, xml, JSON, and html, file formats, images in JPEG, GIF format, audio files in MP3, WAV, WMA, AIFF, M4A, and AAC and videos in MPEG-1, MPEG-2, and MPEG-4, 3GPP, AVI, WMV, FLV, and MOV format – The participating agencies in EDMP include:

· Occupational Safety and Health Administration (OSHA): http://www.osha.gov/index.html

· Mine Safety and Health Administration (MSHA): http://www.msha.gov/

· Wage and Hour Division: http://www.dol.gov/whd/

· Employment and Training Administration: http://www.doleta.gov/

· Design for the future.

· Able to mine, discover and analyze

· Handle emerging forms of data.

· Present the consolidated requirements for a streamlined data collection and standardized ETL process.

· Present the warehouse framework for DOL- one that consolidates data, powers distribution from one place and enables growth initiatives/new products.

· Present the Technology stack. Leverage open technology standards prevalent in industry and federal government wherever possible. Exploit state of the art technology where applicable.

· Develop Process diagrams for a temporary bridging of legacy data capture platforms into the new architecture.

· Create the unified warehouse design based on our vision and collected requirements.

· Should Streamline and centralize BAU activities

· Provide new capabilities and increase efficiency of employees, administrators, researchers and operational staff

· Provide centralized consistent and effective metadata and master data, leveraging existing standards (such as Project Open Data Metadata Schema v1.1 employed across federal agencies https://project-open-data.cio.gov/v1.1/schema/ using the Data Catalog Vocabulary or DCAT ; or standards based on the Dubline Core http://dublincore.org/ ).

· Be inclusive from an architectural perspective, of absorbing and leveraging different data formats and structures [List of data formats to be used in the initial implementation of EDW and EDMP is provided earlier in this section.] Ideal architectures and designs will be extensible, flexible, scalable, and accommodate new data formats and data sources.

· Support ideas and creativity in development of new capabilities in data-driven innovation, decision-making and novel digital services.

· Position the warehouse as the backbone of data-driven decision making

· Complies with all necessary DOL CSH security controls, security and privacy standards, and appropriately addresses the confidentiality, integrity, and availability requirements of the system

· Develop a design proposal for DOL review and approval

· Present written status at weekly meeting

4.4 Build Phase:

· Contractor shall complete all coding for approved warehouse design

· Contractor will provide all models, use cases and test plans for each dimension of the design.

· Contractor shall provide DOL with a detailed testing plan for integrated testing of the data capture and storage mechanism.

· Contractor shall include all metrics and keys provided by DOL on redesigned warehouse.

· Contractor shall conduct testing in both their domain/facility as well as in a limited beta release

· Contractor shall resolve any coding and processing issues identified in testing

· Contractor shall compile a testing report to present to DOL for review/approval

· Present written status at weekly meeting

4.5 Implementation Phase:

· Contractor shall implement the newly redesigned EDMP on DOL servers

· Contractor shall begin providing tier 4- engineering DB support at this point forward until the end of the period of performance for all break fix issues and address them in a timely manner.

· Present written status at weekly meeting

4.6 Project Handoff/Closure:

· Contractor shall provide DOL with all documentation in accordance with the approved project plan

· Contractor shall present project closure report to DOL for review and approval

· Contractor shall define project requirements checklist with DOL and complete the list by demonstrating that all project tasks have been completed

· Present written status at weekly meeting

5.0 Period of Performance The period of performance for this project is one year (365 days). All work must be scheduled to be completed within this timeframe.

6.0 Place of Performance The Contractor will perform the work at the DOL OASAM-OCIO facilities in Washington DC. The Contractor will be required to meet at DOL’s facility once per week (day and time TBD) for a weekly status meeting. Additionally, all project gate reviews will be held at DOL’s facility and attended by the Contractor. DOL will provide and arrange for meeting spaces within its facility for all required Contractor meetings. Once the project reaches the implementation phase, all implementation will be conducted at DOL’s facility.

7.0 Schedule/Milestones For Sample Task The below list consists of the initial milestones identified for this Project:

· Requirements & Key Metric Analysis

· Resource Allocation

· Warehouse Design Review

· Technology Stack presentation and review

· Warehouse Implementation Review

· Project Plan

· Build and Implementation Plan

· Initial Implementation Complete

· Testing and Evaluation

· Final Implementation Complete

· Project Completion Review

· Project Closure/Archives Complete

The Contractor shall propose dates for each milestone identified in the Schedule/Milestones Section above in their proposed solution to the sample task order.

8.0 Acceptance Criteria

For this project the acceptance of all deliverables will reside with DOL’s OCIO COR. The COR and a technical project manager or director at the OCIO-DOL, and the DOL Technical COR will monitor tasks and evaluate progress in order to ensure the completeness of each stage of the project and that the scope of work has been met. Once a project phase is completed and the Contractor provides their report/presentation for review and approval, the COR will either sign off on the approval for the next phase to begin, or reply to the Contractor, in writing, advising what tasks must still be accomplished.

Once all project tasks have been completed, the project will enter the handoff/closure stage. During this stage of the project, the Contractor will provide their project closure report and project task checklist to DOL’s COR. The acceptance of this documentation by DOL’s COR will acknowledge acceptance of all project deliverables and that the Contractor has met all assigned tasks.

Any discrepancies involving completion of project tasks or disagreement between DOL and the chosen Contractor will be referred to both organizations’ contracting offices for review and discussion.

9.0 Required resources For Sample Task DOL estimates that task will take one year to be completed.. The Contractor shall include in their response, an estimate of the level-of-effort with total number of person-hours involving a combination of various skills from the Technical and Business Skill Requirements section, and an estimate of the breakdown of the hours per labor category to complete the task. Contractor shall quote only those personnel possessing qualifications and experience requirements which reflect an ability to perform all responsibilities for the specified labor category, and determine the best combination of skills from the LCATS to execute this task successfully.

10.0 Evaluation Criteria For Sample Task For detailed evaluation criteria used in evaluating the response to the sample task order, the Contractor shall refer to Section M (Evaluation Factors for Award). In addition to the evaluation factors used in Section M, the Contractor should, in their technical response to the sample task, propose dates for each milestone identified in the Schedule/Milestones Section above, and also provide a detailed estimate of the breakdown of the hours per labor category to complete the task.

11.0 Security Requirements

All Contractor project team members will submit security forms to DOL for clearance and access badges to the facility. All Contractor programmers and quality control team members will be granted access to DOL servers and all necessary IT functions. They will also be given temporary DOL accounts which are to be used only for work pertaining to the EDMP Project. Upon completion of the project these accounts will be closed.

Statement of Work- Department of Labor.

PAGE