FRA_Draft_RSIMSS_RFP_(7-16-15)_(Rev._1).docx

SECTION B – SUPPLIES OR SERVICES AND PRICES AND COSTS

B.1 DESCRIPTION OF SERVICES

The U.S. Department of Transportation (USDOT), Federal Railroad Administration (FRA), Office of Railroad Safety provide services to maintain and streamline its safety data management support services requirement, herein referred to as Railroad Safety Information Management Support Services (RSIMSS).The FRA maintains railroad safety data dating back to 1975 as part of its safety mission. The reporting, data management, and data analysis processes have evolved over time into an overarching safety data program known as the Railroad Safety Information System (RSIS). This data is collected through mandatory railroad reporting, voluntary reporting, and FRA and State inspection reporting. The data is comprised of accident/incident data, grade crossing inventory data, inspection and accident investigation data, and other plans and reports. The majority of safety data collected and managed via the RSIS program is regulation data. This data is mandated to be collected and maintained by office of safety (specifically, FRA Chief Safety Officer) and has the specifics regarding format and submission method detailed through the rulemaking process.

The following are the three (3) task for the RSIMSS requirement:

a) Data Collection, Data Processing, and RSIS Data Solution Operations and Maintenance

b) Non-Routine Maintenance, System Development and Enhancements

c) Transition services, which will support the transition of tasks to a new contractor, if required

B.2 SCHEDULE OF PRICING

Base Period of Performance: December XX, 2015 through December XX, 2016 Task Order CLIN Structure

(FFP)

UNIT

(FFP)

TOTAL PRICE

(FFP)

QTY or ESTIMATED HOURS

(LH)

FULLY LOADED HOURLY

LABOR RATES (Cumulative)

(LH)

NTE ESTIMATED PRICE

(LH)

Contract Line Item Numbers (CLIN) 00001, 00003 and 00004 shall be Firm-Fixed Price (FFP) CLINs. CLIN 00002 shall be a predominately Firm-Fixed Price CLIN with the capacity and option for Labor Hour (LH) Task Orders to be issued against the CLIN 00002, if required. The Government will determine the most appropriate Task Order type FFP or LH, for CLIN 00002. LH CLIN 2 Task Orders shall be awarded with an established Not-To-Exceed (NTE) price ceiling and Task Order final price shall be accomplished utilizing the established labor rates herein.

The following are suggested labor categories over the course of the Base Period of Performance, although the contractor may suggest their own mix of labor categories:

· Project Manager*

· Deputy Project Manager*

· Task Lead

· Senior Data Analyst

· Senior Solution Manager

· Data Analyst

· Technical Writer

· Documentation Specialist

*These are key personnel.

LABOR HOUR PRICING SCHEDULE FOR BASE PERIOD

LABOR HOUR PRICING SCHEDULE FOR OPTION YEAR ONE

Option Year One Period of Performance: December XX, 2016 through December XX, 2017 Task Order CLN 1 Structure

(FFP)

UNIT

(FFP)

TOTAL PRICE

(FFP)

LABOR RATES (Cumulative)

(LH)

NTE ESTIMATED PRICE

(LH)

Contract Line Item Numbers (CLIN) 10001, 10003 and 10004 shall be Firm-Fixed Price (FFP) CLINs. CLIN 10002 shall be a predominately Firm-Fixed Price CLIN with the capacity and option for Labor Hour (LH) Task Orders to be issued against the CLIN 10002, if required. The Government will determine the most appropriate Task Order type, FFP or LH, for CLIN 10002. LH CLIN 1 Task Orders shall be awarded with an established Not-To-Exceed (NTE) price ceiling and Task Order final price shall be accomplished utilizing the established labor rates herein.

The following are suggested labor categories over the course of Option Year One, although the contractor may suggest their own mix of labor categories:

· Project Manager*

· Deputy Project Manager*

· Task Lead

· Senior Data Analyst

· Senior Solution Manager

· Data Analyst

· Technical Writer

· Documentation Specialist

*These are key personnel.

LABOR HOUR PRICING SCHEDULE FOR OPTION YEAR TWO PERIOD

Option Year Two Period of Performance: December XX, 2017 through December XX, 2018 Task Order Structure

(FFP)

UNIT

(FFP)

TOTAL PRICE

(FFP)

QTY or ESTIMATED HOURS

(LH)

FULLY LOADED HOURLY

LABOR RATES (Cumulative)

(LH)

NTE ESTIMATED PRICE

(LH)

Contract Line Item Numbers (CLIN) 20001, 20003 and 20004 shall be Firm-Fixed Price (FFP) CLINs. CLIN 20002 shall be a predominately Firm-Fixed Price CLIN, with the capacity and option for Labor Hour (LH) Task Orders to be awarded against the CLIN 20002, if required. The Government will determine the most appropriate Task Order type, FFP or LH, for CLIN 20002. LH CLIN 2 Task Orders shall be awarded with an established Not-To-Exceed (NTE) price ceiling and Total Prices shall be accomplished utilizing the established labor rates herein.

The following are suggested labor categories over the course of Option Year Two, although the contractor may suggest their own mix of labor categories:

· Project Manager*

· Deputy Project Manager*

· Task Lead

· Senior Data Analyst

· Senior Solution Manager

· Data Analyst

· Technical Writer

· Documentation Specialist

*These are key personnel.

LABOR HOUR PRICING SCHEDULE FOR OPTION YEAR THREE

Option Year Three Period of Performance: December XX, 2018 through December XX, 2019 Task Order CLN 3 Structure

(FFP)

UNIT

(FFP)

TOTAL PRICE

(FFP)

QTY or ESTIMATED HOURS

(LH)

FULLY LOADED HOURLY

LABOR RATES (Cumulative)

(LH)

NTE ESTIMATED PRICE

(LH)

Contract Line Item Numbers (CLIN) 30001, 30003 and 30004 shall be Firm-Fixed Price (FFP) CLINs. CLIN 30002 shall be a predominately Firm-Fixed Price CLIN, with the capacity and option for Labor Hour (LH) Task Orders to be issued against the CLIN 30002, if required. The Government will determine the most appropriate Task Order type, FFP or LH, for CLIN 30002. LH CLIN 2 Task Orders shall be issued with an established Not-To-Exceed (NTE) price ceiling and Total Price shall be accomplished utilizing the established labor rates herein.

The following are suggested labor categories over the course of Option Year Three although the contractor may suggest their own mix of labor categories:

· Project Manager*

· Deputy Project Manager*

· Task Lead

· Senior Data Analyst

· Senior Solution Manager

· Data Analyst

· Technical Writer

· Documentation Specialist

*These are key personnel.

LABOR HOUR PRICING SCHEDULE FOR OPTION YEAR FOUR

Option Year Four Period of Performance: December XX, 2019 through December XX, 2020 Task Order CLN 4 Structure

(FFP)

UNIT

(FFP)

TOTAL PRICE

(FFP)

QTY or ESTIMATED HOURS

(LH)

FULLY LOADED HOURLY

LABOR RATES (Cumulative)

(LH)

NTE ESTIMATED PRICE

(LH)

Contract Line Item Numbers (CLIN) 40001, 40003 and 40004 shall be Firm-Fixed Price (FFP) CLINs. CLIN 40002 shall be a predominately Firm-Fixed Price CLIN, with the capacity and option for Labor Hour (LH) Task Orders to be issued against the CLIN 40002, if required. The Government will determine the most appropriate Task Order type, FFP or LH, for CLIN 40002. LH CLIN 2 Task Orders shall be issued with an established Not-To-Exceed (NTE) price ceiling and Total Price shall be accomplished utilizing the established labor rates herein.

The following are suggested labor categories over the course of Option Year Four although the contractor may suggest their own mix of labor categories:

· Project Manager*

· Deputy Project Manager*

· Task Lead

· Senior Data Analyst

· Senior Solution Manager

· Data Analyst

· Technical Writer

· Documentation Specialist

*These are key personnel.

LABOR HOUR PRICING SCHEDULE FOR OPTION YRAR FOUR

B.2.1 Additional Pricing Guidance for Applicable to All Schedule of Pricing (Base and Option Period of Performance) Firm Fixed Price Total and Labor Hour Prices shall be inclusive of total allowable costs, i.e., fully loaded hourly rates.

B.3 MINIMUM GUARANTEE

B.3.1 The minimum guarantee value for this requirement is $1,500,000.00 over the life of the contract.

END SECTION B

SECTION C – DESCRIPTION/SPECIFICATIONS/STATEMENT OF OBJECTIVES

C.1 Definition – Statement of Objectives

Per Federal Acquisition Regulations, Subpart 2.1, Definitions -Statement of Objectives (SOO)” means a Government-prepared document incorporated into the solicitation that states the overall performance objectives. It is used in solicitations when the Government intends to provide the maximum flexibility to each offeror to propose an innovative approach.

C.2. Background Information C.2.1 The United States Department of Transportation (DOT) Federal Railroad Administration (FRA) Office of Railroad Safety has a need for data and knowledge management support services, hereinafter referred to as Railroad Safety Information Management Support Services (RSIMSS) that will enable sound data management practices and consistently high quality delivery of railroad safety and safety-related data, hereafter aggregately railroad safety data, and information assets to FRA and its stakeholders.

FRA maintains railroad safety data dating back to 1975 and the reporting, data management, and data analysis processes have evolved over time into an overarching safety data program known as the Railroad Safety Information System (RSIS). The majority of safety data collected and managed via the RSIS program is regulation data. This data is mandated to be collected and maintained by Office of Safety (specifically, FRA Chief Safety Officer) and has the specifics regarding format and submission method detailed through the rulemaking process. The Railroad Safety information Management Division (RSIMD) has the mission of planning and directing all activities relating to the management of the Office of Safety’s information assets and use of the data, ensuring availability and accuracy of the railroad safety knowledge resources, and serving as the authoritative source.

To achieve the vision of maintaining a single authoritative data source for railroad safety data, RSIMD has undertaken a number of projects focusing on its principal safety data system, RSIS, and its underlying data structure. RSIS is comprised of a series of subsystems for housing and processing various data types with some integration across datasets. The principal subsystems include:

Railroad Accident/Incident Reporting System (RAIRS) comprising railroad accident/incident data, highway-rail collision data, operational data, and injury and illness data required under 49 CFR Part 225 Railroad Inspection Reporting System (RIRS) comprising compliance and enforcement data including defects and proposed violations collected through FRA and State inspections Highway-Rail Grade Crossing Inventory System (GCIS) comprising inventory, equipment, and characteristic information about highway-rail crossing intersections.

In addition to the principal subsystems, RSIS also maintains safetydata portals (public and secure/private) to disseminate and distribute railroad safety data, reports, and information to its stakeholders, an investigation reporting system for collecting accident investigation reports, a SharePoint portal for collecting data and information not falling into the three primary datasets (such as required railroad plan submissions with routing and approval workflow), and various other data management solutions such as the Activation Failure/ False Proceed (AF/FP) report for recording AF/FP investigations. More details about RSIS and a complete list of applications and systems contained within can be found in Attachment 2.

Historically, RSIMD was primarily focused on getting the data on time into RSIS; however, RSIMSS will enable RSIMD to perform the requisite planning, analysis, and enhancement with an emphasis on streamlining the data collection processes from a business perspective. The optimization of processes and integration of datasets will shift the paradigm of the safety data collection program and will require modern, flexible solutions that can be accessed from a variety of methods across data stakeholder groups. A goal of these efforts will be to generate efficiencies in all aspects of the data management process including operations, maintenance, and enhancement and position RSIS to be a platform that enables the uploading, analysis, and distribution of FRA safety data and information to FRA’s stakeholders.

C.3 Envisioned Scope

C.3.1 The primary scope and objective of the resulting RSIMSS contract will provide safety data management support services that will enable FRA to accomplish mission objectives. This SOO is designed to provide Contractors with a framework of efficient and highly effective services to fulfill the safety data management needs from the data collection process through data strategy development and implementation and subsequent safety data management tool maintenance for the next five years. The main focus will be around establishing an efficient data management solution and schema to enable the publishing of data and the framework for a data exchange between FRA and its stakeholders, while striving for continuous improvement.

C.3.2 FRA will use an Indefinite Delivery, Indefinite Quantity (IDIQ) contract vehicle for the RSIMSS contract and include the following support service areas to support the overall contract objectives:

Safety Data Management Support Services Safety Data Collection Support Services Safety Data Management Program Planning Support Services Safety Data Distribution and Data Analysis Support Services Safety Data Business Process Improvement and Optimization Support Services Safety Data and Information Communications and Data Delivery Support Services C.4 RSIMSS Objectives

C.4.1 The RSIMSS will enable FRA to achieve the following objectives:

C.4.1.1 Advance the railroad safety data management program to meet current and future safety data and information needs of the inspection, enforcement, compliance, accident/incident, and grade crossing inventory regulatory requirements

C.4.1.2 Provide comprehensive regulatory support for maintaining current and future safety data collection requirements and developing and implementing new regulatory data requirements

C.4.1.3 Support operational and business process updates to maximize efficiency, safety data quality, safety data analysis, and information availability

C.4.1.4 Ensure the best practical and cost-effective technology tools are applied to meet FRA’s current and future safety data management and analysis needs, through a continuous improvement process

C.4.1.4 Ensure uninterrupted FRA safety data mission delivery to the FRA data stakeholders and citizens

C.4.1.5 Ensure proper maintenance of the RSIS data management programs and tools and providing transparent input to FRA’s change management processes, investment lifecycle processes, and security processes

C.4.2.The target RSIS state can be defined with three main goals, which are supported by the RSIMSS:

C.4.1 Data Integration – Implement an integrated data structure to support and streamline reporting and analysis C.4.2 2 Data Collection and Quality – Implement data validation and data quality checks at the point of entry to ensure valid and consistent data for internal FRA inspection and investigation reporting as well as external stakeholder data reporting

C.4.2.3 Data Distribution – Streamline the data distribution and delivery process and provide more valuable information to external and internal stakeholders and user groups to include Application Programming Interfaces (APIs) and other data delivery provisions C.5 Tasks

The tasks are divided into four contract line items (CLIN) as follows:

Data Collection, Data Processing, and RSIS Data Solution Operations and Maintenance, which will be activated at the time of contract award as a Firm Fixed Price (FFP) task

Railroad Safety Information Management Support Services, which is a CLIN structured as an IDIQ for procuring support services in a flexible manner using Firm Fixed Price, Fixed Rate, or any combination thereof for tasks.

Transitioning In, which will support the transition of tasks to a new contractor or FRA as required, using Firm Fixed Price.

Transitioning Out, which will support the transition in support of the termination of the contract

C.5.1 CLIN 001 – Data Collection, Data Processing, and RSIS Data Solution Operations and Maintenance Objectives

The scope of CLIN 001 is to procure, on a Firm Fixed Price basis, contractor services to manage the collection, acceptance, validation, entry, processing, storing, and publishing of all railroad safety data and to perform day-to-day data management, operations, and maintenance activities required to ensure the data management solutions that are integrated with and enable the data collection and processing activities are maintained and functioning efficiently.

The overarching objective of this effort is to provide and maintain an authoritative Railroad Safety Information System (RSIS).

C.5.1.1 Management Objectives

The management objectives of CLIN 001 are to:

Enable the contractor maximum flexibility to innovate, identify and propose the data management process and solutions to manage program performance, cost, and risk and deliver an effective and affordable RSIS which, Maintain clear government visibility into program cost, schedule, technical performance, and risk Continually re-evaluate program effectiveness and provide periodic recommendations to the government for efficiencies that can be gained through process optimization and technology integration Support the government with regulatory requirement gathering and provides data solution recommendations to meet those requirements

C.5.1.2 Technical Objectives

The technical objectives of CLIN 001 are to:

Collect and distribute railroad safety data Enable transparent and open data exchange (i.e. an API first approach) with FRA stakeholders including the public, industry, and other government agencies and bodies Align data management processes and solutions with the DOT and FRA data management strategy Continuously propose and improve the operational efficiency of the data collection and data management solutions encompassed within the RSIS program Comply with Federal, DOT, and FRA requirements

C.5.1.3 Performance Objectives C.5.1.3.1 Project Management Objectives The project management objectives are to (i) provide support for overseeing resource management activities to include budgeting, programming and accounting; (ii) provide support for development, preparation, submission, and justification of budget exhibits and request for information for FRA’s A-11 Capital Planning and Investment Control (CPIC) requirements.

C.5.1.3.2 Project Visibility Objectives The objectives are to enable government insight into program performance through (i) clear and concise work breakdown structures; (ii) a regularly updated and integrated project plan measured against the baseline; (iii) utilize generally accepted best practice management reports to identify potential schedule risks and cost overruns; and (iv) status reports with issues, risks and mitigation strategies.

C.5.1.3.3 Program Effectiveness Objectives The objectives are to identify the overall effectiveness of the RSIS program in support of the FRA safety mission and (i) identify gaps and propose improvements to the program to better support FRA’s safety mission and FRA’s stakeholders; (ii) support FRA when implementing program changes; and (iii) identify continuous process improvement.

C.5.1.3.4 New Regulation Objectives The objectives are to pro-actively support the rulemaking process to identify RSIS program and solution impacts and (i) assess data and technical requirements of proposed rulemakings to identify impacts to RSIS; (ii) plan for updating the data collection process, data management tools, or data management solutions; and (iii) implement routine data management solution changes as part of this task or support the government with determining cost, scope, and schedule for any larger changes to be performed as an RSIS enhancement under CLIN 002.

C.5.1.3.5 Data Collection Objectives The objectives are to promote railroad safety through the following: (i) collect, assess, manage, and report on safety data; (ii) enable FRA to determine the effectiveness of safety programs through data availability and quality to support an overall reduction in the number of train accidents and incidents per million train miles; (iii) provide timely distribution of railroad safety data to FRA management, government agencies, railroad labor and management, and the general public; (iv) provide data resources to interfacing programs, such as National Inspection Plan (NIP), and to support a valid statistical method of determining which highway railroad crossings are eligible to receive funds to improve warning systems; (v) record enforcement actions on regulatory violations and identify leading causes of accidents and injuries; (iv) support the determination of systemic problems (both self-reported and those reported by Federal and state inspectors) and defective conditions of the railroad system; and (v) track and report on industry defect remediation activities.

Safety data includes accident data, incident data, highway-rail grade-crossing inventory data, operational data, inspection data, violation data, investigation data, other railroad safety regulatory and non-regulatory data and plans, etc.

C.5.1.3.6 Data Exchange Objectives The objectives are to enable open, transparent, and two-way data exchange with FRA stakeholders including DOT and Modes, Railroad and related industries, other federal agencies, state and local governments, and citizens as determined appropriate by FRA. The objectives include the contractor (i) provide railroads with a secure method to access FRA inspection and violation data for railroads to track and remediate deficiencies; (ii) provide the public with a method to access railroad safety data including accidents and incidents, and highway-rail crossing data; (iii) provide the capability to run dynamic queries, download railroad safety data, and view current statistical information on railroad safety; (iv) provide FRA and state partners a secure method to review accident, casualty, inspection, and other data to assist management and other decision makers in taking the right actions to promote safety within the railroad industry.

C.5.1.3.7 Process Effectiveness Objectives The objectives are to identify efficiencies in the process, tools, or solutions used over the duration of this task to achieve cost or performance efficiencies and (i) implement process efficiencies transparent to the data reporting or data users; (ii) recommend technology or user-impacting process changes for government consideration; and (iii) support regulatory process with information and analysis justifying those changes.

C.5.1.3.8 Compliance Objectives The objectives are to (i) achieve and maintain compliance with IT Governance Policies as required under Federal, DOT and FRA regulations and policies, as updated, including but not limited to OMB Circular A-130; the Federal Information Security Management Act (FISMA) of 2000, and as identified in the National Institute of Standards and Technology (NIST) Guidelines, (ii) align and support the FRA Enterprise Architecture (EA) policies consistent with the Federal Enterprise Architecture reference models; and (iii) align and support the DOT and FRA Data Management Strategy.

C.5.2 CLIN 002 – RSIS Data Management Services and Data Solution Enhancement Services Objectives

The scope of services and support described under this CLIN will be conducted under the RSIMSS IDIQ. Consistent with the scope and purpose of the contract, the contractor shall provide a full and complete range of technical and professional support to FRA to assist with any and all aspects of collecting, processing, storing, maintaining, validating, and analyzing data; planning, designing, testing, and implementing data management tools; and supporting administrative functions ensuring all data management tools comply with FRA and DOT capital planning, enterprise architecture, and security policies. FRA’s designated Contracting Officer, in consultation with the FRA Chief Safety Officer or designee, will make the final determination of whether a requested type of support not specifically addressed herein may be performed and considered within scope. Any new maintenance requirements, as the result of enhancements, will be covered under this CLIN until conclusion of the option year, at which time this maintenance will be covered under CLIN 001.

C.5.2.1 Safety Data Management Support Services The FRA collects and maintains railroad safety data dating back to 1975 as part of its safety mission. This data is collected through mandatory railroad reporting, voluntary reporting, and FRA and State inspection reporting and is comprised of accident/incident data, railroad operational data, highway-rail grade crossing inventory data, inspection and investigation data, and other plans and reports. Although the FRA safety data management program is a mission-oriented program, data management tools are an important part in achieving the mission and evolving the data into information assets to assist in data-driven decision making for FRA operations and to inform the regulatory process of necessary changes or new regulations required to enhance railroad safety. These tools are tightly coupled with the data collection, data management, and data delivery business processes, and are integral to achieving the mission objectives of RSIS.

The following are objectives of the Safety Data Management support services:

Modernize, enhance and develop data solutions, documentation, configuration management, and testing in accordance with industry best practices and FRA/DOT policy with increasing efficiency and cost effectiveness Support changing mission needs, regulatory requirements, analysis requirements, or realize efficiencies by performing requirements analysis, supporting the regulatory process, identifying opportunities, and enhancing data solutions or tools accordingly Increase the program performance by utilizing modern methodologies and an API-first approach to effectively and efficiently implement enhancements or new solutions Perform complete requirements documentation, implementation, and testing in accordance with industry best practices and FRA/DOT policy and in alignment with the chosen methodology for any approved or procured enhancements

Data management tools and solutions in support of the data collection process, spans various languages and platforms may include .NET, SQL, SQL Server, PL/SQL, SAS, Visual Basic, JQuery, SharePoint, Java, Javascript , C++, AJAX, HTML, HTML5, CSS3, XML, JSON, ODATA, SOAP, REST, ESRI, ArcGIS Server, API’s, data modeling, Oracle 11gR2 database, Oracle Web Server 10g, JavaServer Pages, Struts, Oracle 10g Developer Suite for case generation reports, Redhat Linux Enterprise 7, and other modern languages for application maintenance activities. Note: the servers on which the databases reside are managed and maintained by FRA. The contractor will have to follow the FRA Change Control Board process.

C.5.2.2 Data Collection Support Services The regulation and focus of FRA safety data collection changes over time as the rail industry operations and technology and safety trends are adopted. FRA has a requirement to be able to implement changing regulation requirements or implement process efficiencies within the RSIS data collection and management processes. The objectives of the Data Collection Support Services task area are to:

Provide support for changing or updating data collection processes as required based on changing FRA mission or regulatory requirements to include interfacing and communicating with railroad reporting officers, FRA and State inspectors, and other FRA stakeholders Modify processes and perform data collection processing based on new requirements to include data acquisition, data validation, data quality assurance, exception reporting, data conversion, data distribution, data delivery, data availability, and process performance, tracking and reporting During ongoing data management operational and enhancement efforts under this service area and other service areas, FRA expects the contractor to provide recommendations and opportunities for making the data collection process more efficient. A focus of these recommendations should be on business process improvements to achieve operational efficiencies, realize strategic initiatives, and implement new mission and regulation requirements.

C.5.2.3 Safety Data Management Program Planning Support Services RSIMD is seeking to strengthen its safety data and safety related data planning functions and operations in meeting regulatory and safety mission requirements. Strategic planning is an organization’s process of defining its strategy or direction and making decisions on allocating its resources in pursuit of this strategy, including both capital and people. The FRA is currently undergoing an enterprise data management assessment and will be issuing a data management strategy. The objectives of this service area are to:

Support FRA strategic goals by ensuring the RSIMSS program aligns RSIS with those programmatic and strategic goals and objectives Support the alignment of RSIS to goals and objectives in DOT’s and FRA’s enterprise data management strategies Provide a broad range of technical and professional services to support Office of Safety’s data management program planning function and operations Provide support and analyses, evaluations, strategic recommendations, and recommendations for plans of actions to assist in identifying and articulating strategies for achieving FRA’s safety data priorities; assess safety data management maturity and provide recommendations to develop an action plan to meet mission needs and adopt future data management trends, and providing advice on the implications of implementing new trends or tools with a focus on open source, cloud-based, or low/no-code solutions aligning to the White House’s Open Government Initiative Enhance RSIMDs strategic and program planning for safety data management programs including program performance, developing plans and roadmaps for RSIMD safety data management business and technical architectures that conform to mission goals, transform the RSIMD organization, and align to acceptable risk tolerance Enhance RSIMD’s analytical capability through performing scenario and trend analysis, performing cost-benefit analysis, and supporting the development and implementation of the data management program plan and strategic plan Provide support for all regulatory mandate initiatives involving safety data

The contractor shall be knowledgeable of, and experienced in, applying data management and planning best practices to the public and private sector. In researching, assessing, and planning for new solutions and techniques, the contractor shall perform, obtain, and use long-term strategic assessments, projections, and trend analysis. The contractor shall map out possible outcomes for implementation and analyze their impact on the needs and capabilities of FRA to better use its data assets.

C.5.2.4 Data Distribution and Data Analysis Support Services RSIMD provides stakeholders with safety data using various distribution and delivery methods and also provides data reporting and analysis for internal and external stakeholders. This data analysis can be delivered in various ways either through the creation of an ad-hoc report to a more permanent data delivery web-based query for those reports with more frequent requests. As a result, RSIMD is seeking contractor support for enhancing and complementing its data distribution and data analysis functions. The objectives of the Data Distribution and Data Analysis service area are as follows:

Support the alignment of FRA’s safety data assets to changing mission priorities, establishment of a flexible platform supporting FRA safety data analysis activities, and the performing of data analysis to provide safety information to FRA safety data stakeholders Provide expertise and support to mature the RSIS analytical capability beyond trends analysis, based on historical data, with an objective of enabling predictive analytics and risk indicator analysis Providing support for the transforming, merging, processing, and making available data for use in data analysis activities through updates to reports, capabilities, features, functions, and data integration to make the data more useful, more easily accessed or analyzed, and more capable

The contractor shall have experience with modern data analysis tools including graphical visualizations, dashboards, data mashups, and other techniques for communicating complex information in simple and easy to understand reports. The contractor shall be familiar with the state-of-the-art and understand industry best practices to provide recommendations for the appropriate tool or technique for the requested outcome and have experience performing alternatives analysis and business case analysis to back up the recommendation.

C.5.2.5 Safety Data Business Process Improvement and Optimization Support Services The RSIMD safety data collection process is largely constrained by current Federal Regulation, however there are a number of processes to ingest, validate, process, store, and publish various pieces of safety data, which encompasses the full data management lifecycle. The objectives of the Safety Data Business Process Improvement and Optimization service area are as follows:

Support FRA with expertise in business process analysis, improvement, and optimization for assessing the as-is safety data business processes, defining to-be safety data business processes, performing gap analyses, and identifying roadmaps for achieving the to-be safety data business process design Identify and implement performance metrics for RSIMD data management programs and operations to measure process effectiveness, program performance, and operational efficiency Identifying efficiency, capability, and automation opportunities for existing safety data business processes and assessing required process, organizational, and technology changes for suitability for FRA’s safety culture, risk tolerance, and cost-benefit Implement safety data process improvement changes and monitor performance improvement

The contractor shall have experience with data management, customer interface, change management, and business process re-engineering and should be familiar with modern workflow and automation tools that may be implemented as part of the process improvement effort. The contractor shall be able to discuss detailed cost-benefits of the process changes, risks associated with making and not making changes, and analysis of alternative options.

C.5.2.6 Data and Information Communications and Data Delivery Support Services An important aspect of the FRA safety mission is stakeholder outreach and communications. The contractor shall provide a broad range of technical and professional services to support FRA safety data communications. The objectives of the Data and Information Communications and Data Delivery service area are as follows:

Planning, analyzing, designing, developing, implementing, and managing communications strategies, plans, products, tools, and services Engaging with internal FRA stakeholders in a persistent manner and position RSIMD to have an active presence in the FRA and DOT data management community through the coordination and scheduling of meetings and communications activities Managing, developing, and publishing safety data and other communications assets Increasing the reach of FRA safety data to internal, industry, state, and other stakeholders through more active communications campaigns

The contractor shall have experience with data distribution and data delivery, communications, internal and external marketing and user engagement, developing communications plans and assets, and developing language and graphics suitable for electronic publishing accounting for accessibility constraints (i.e. Section 508 and WCAG 2.0 compliance) on FRA safetydata sites C.5.2.7 Required Expertise The contractor shall demonstrate experience in each of the above capability areas. Additionally, the contractor shall demonstrate:

The ability to work with customers to assess needs, provide assistance, resolve problems, and satisfy expectations Knowledge of safety programs; safety data management, analysis and use; FRA programs and mission; methods, metrics, tools, technology, and techniques for business process improvement and data management Understanding of principles, methods, or tools for maintaining data management solutions, enhancing existing data management solutions, and developing new data management solutions Understanding of methods and tools for managing projects and programs using various project management methodologies Understanding of information assurance, cybersecurity, privacy policies, records management, and best practices Understanding of White House and OMB initiatives related to open data, digital government, IPv6, and other relevant initiatives

CLIN 003 – Transition In Support Services

The successful contractor shall conduct a complete turnover with the incumbent contractor. The government anticipates that one (1) month will be required. Turnover shall include all government furnished information, government data, and government furnished equipment (as required.) This shall occur under the direction of the COR to ensure a seamless transition of all services for the entire RSIS and subsystems as the Federal Acquisition Regulation (FAR) clause number 52.237-3 (JAN 1991), Continuity of Services applies and in addition:

Phase-In: In accordance with the FAR, the Contractor shall begin the transition phase-in at the start of the contract; however, the Contractor has the option to begin the phase-in transition sooner at no cost to the Government, provided the contract is awarded. During this transition period, the Government will make available to key incoming Contractor personnel, a Government representative familiar with the operations and functions to be performed in relation to security systems operation, maintenance and technical support services. The Contractor shall become familiar with the contract requirements in order to commence full performance on the Contract Start Date. All work covered by this contract that was started but not completed by the Government or its Contractor by the Contract Start Date, shall become the complete responsibility of the Contractor for continuity of service.

5.4 CLIN 004 – Transition Out Support Services

Phase-Out: To ensure a smooth transition to the successor Contractor and to prevent possible decreases in productivity or service quality, the Contractor shall, up to 30-calendar-days before contract termination date, furnish phase-in training. During this period, the Contractor shall make available to key incoming Contractor personnel, a representative of the incumbent Contractor that is versed in the operation of the functions to be performed. The incumbent Contractor shall provide required training and transfer material, equipment, and/or tools as required by the existing and/or new contract. The incumbent Contractor shall conduct joint inventory with the Government representative(s) and representatives of the incoming Contractor.

C.6 Management and Staffing

The contractor shall appoint an RSIMSS Project Manager (PM) and Deputy PM who interface directly with the Contracting Officer’s Representative (COR) and the RSIS System Owner to ensure that work requirements are met on schedule and that the Contractor produces accurate/quality products as efficiently as possible. The PM will be directly involved in all aspects of contract management and personal interactions with government staff are expected. The PM will regularly review and communicate, at all stages, the progress or status of contract and task order items with the COR and RSIS System Owner to ensure adequate delivery and quality.

C.6.1 Policies and Procedures Contractor personnel must adhere to current and future Government policies and procedures in the performance of their duties. These policies and procedures include but are not limited to; Standard Operating Procedures, Security Policies, Project Management Life Cycle Methodology, Systems Development Life Cycle Methodology, etc. All liability will rest with the contractor personnel.

C.6.2 Key Personnel Key Personnel and/or facilities may be designated on a Task Order basis, with the exception of the PM and deputy PM. All personnel considered “Key” must be specifically designated as such in the executed TOs. All key personnel are subject to approval by the COR and/or System Owner.

C.6.2.1 Project Manager (Key Personnel) At a minimum, the project manager must:

Be able to demonstrate successful prior government consulting experiences in providing guidance and direction in resolving complex program management and organizational problems Possess a PMP or CPM, a minimum of 10 years of experience, with a minimum of 5 years managing a project of similar size, scope, and complexity Experience in application development projects and data management projects Exhibit capabilities in achieving objectives and solving problems in creative, resourceful, and innovative ways Experience working with senior government executives to identify and recommend organizational goals, and how to achieve the goals by using various methodologies and technologies Demonstrate innovative ways to resolve stakeholders’ conflicting requirements Demonstrate capability to provide a complex solution that is flexible enough to accommodate changes in technology Identify existing or emerging technological challenges to satisfy mission goals and objectives Provide strategic planning and guidance on the evolution of business processes and system architectures, and the adoption of new technologies

C.6.2.2 Deputy PM (Key Personnel) The deputy PM assists the PM in managing day-to-day contracting activities, will oversee the daily operations, and be able to back fill in the event the PM is unavailable. At a minimum, the deputy PM must:

Possess a minimum of 3 years of experience managing projects Experience in application development projects and data management projects Exhibit capabilities in achieving objectives and solving problems in creative, resourceful, and innovative ways Experience working with government clients to gather requirements, establish goals and manage delivery Demonstrate innovative ways to resolve stakeholders’ conflicting requirements Demonstrate capability to provide solutions based on changing needs

C.6.3 Staff Performance/Replacement The contractor shall provide a resume for each candidate proposed as key personnel on the IDIQ and any Task Order response Proposed key personnel are tied to contract and task award The Government reserves the right to judge the technical skill and competence of the individual and to require the individual’s replacement if the individual’s qualifications or performance are judged to be deficient at any time with written notification to the Contractor The Government reserves the right to judge the qualifications and acceptability of any individual proposed by the Contractor for any positions, and may require the Contractor to replace an individual whose qualifications and suitability are judged to be deficient with written notification to the Contractor The Contractor agrees the performance of work and services pursuant to the requirement of this contract shall conform to high professional and ethical standards. The Contractor also agrees to remove any employee whose conduct or performance is such that retention would not be in the best interest of the Government as determined by the Project Officer, COR and Contracting Officer

Roles

Offerors, in their management approach, should identify the roles, levels of experience for those roles, and fully burdened labor rates as labor categories they believe will be needed for accomplishing and providing the data management services specified in this SOO. The approach should identify which functions are anticipated being accomplished by each of those roles. Additionally, Offerors should provide in their cost proposal rates for each of the roles identified as a labor category for base year and four option years.

Resumes

Offerors must provide one sample resume for each non-key labor category proposed. Offerors must provide a resume for the Project Manager and Deputy Project Manager as key personnel tied to contract award. Resumes should be a maximum of two (2) pages each. Additional key personnel will be identified at the task order level and will require resumes for any roles indicated as such.

Government Furnished Equipment (GFE) and Asset Requirements

At FRA discretion, the incumbent, under direction of FRA, will transition any government furnished equipment and the entire source codes to the winning offeror. The offeror will provide an equipment transition plan within 90 days to FRA, detailing how they will transition from GFE to offeror owned equipment within 6 months of contract award. Virtual Desktop Interface (VDI) accounts will be provided by FRA to the offeror’s staff who require access to the DOT network. The offerors shall propose the number of personnel they believe will require DOT VDI access. Workstations may be provided on an as-needed basis to those staff that may require specific client applications or otherwise where VDI alone is insufficient to perform the requirements of the SOO. The offerors shall propose the number of personnel they believe will require DOT provided workstations.

The figure below demonstrates the current separation of equipment and environments (provided for reference). In addition, the FRA environment also contains a test environment for testing applications prior to deployment to staging or production.

Figure 1: RSIS Environment Separation The FRA shall retain ownership of all…