HQ0034-19-R-0085-P00001.pdf
PDF 139 KB Posted
- Attached to
- Data Mining SaaS IDIQ
- Solicitation number
- HQ0034-19-R-0085
- Issued by
-
DOD Washington Headquarters Service
About this file
This amendment to a solicitation clarifies labor category education and experience requirements for a data mining software-as-a-service indefinite-delivery, indefinite-quantity contract. The solicitation seeks a prime contractor to provide a standardized, curated group of relevant government and commercial datasets already integrated on a software-as-a-service platform. The contractor must also supply data analysis services and link licensed data to various Department of Defense data sources. The amendment corrects the analyst and data scientist labor categories to require a master's degree with ten years of experience, or a PhD with five years of experience. The pricing spreadsheet was also updated to reflect this change.
Amendment 1_Revised Solicitation
View the file
Other files
| File | Type | Posted |
|---|---|---|
| Data_Mining_Labor_Category_Pricing_with_Descriptions_Correction.xlsx | XLSX spreadsheet | |
| HQ0034-19-R-0085-0002.pdf | ||
| Data_Mining_Labor_Category_Pricing_with_Descriptions.xlsx | XLSX spreadsheet | |
| Data_Mining_Labor_Category_Pricing.xlsx | XLSX spreadsheet | |
| HQ0034-19-R-0085_Questions_and_Answers.xlsx | XLSX spreadsheet | |
| Data_Mining_Pricing_Spreadsheet.xlsx | XLSX spreadsheet | |
| HQ0034-19-R-0085.pdf |
On GovTribe
Work with this file
- Download the original file
- Contacts named in this file
- Similar government files
- Ask GovTribe AI about this file
Text version
AMENDMENT OF SOLICITATION/MODIFICATION OF CONTRACT
Except as provided herein, all terms and conditions of the document referenced in Item 9A or 10A, as heretofore changed, remains unchanged and in full force and effect.
15A. NAME AND TITLE OF SIGNER (Type or print)
30-105-04EXCEPTION TO SF 30
APPROVED BY OIRM 11-84
STANDARD FORM 30 (Rev. 10-83) Prescribed by GSA
FAR (48 CFR) 53.243
The purpose of this amendment is to include the Q&A and update the solicitation to reflect clarif ications made in the Q&A.
1. CONTRACT ID CODE PAGE OF PAGES
Y 1 25
16A. NAME AND TITLE OF CONTRACTING OFFICER (Type or print)
16C. DATE SIGNED
BY 24-May-2019
16B. UNITED STATES OF AMERICA15C. DATE SIGNED15B. CONTRACTOR/OFFEROR
(Signature of Contracting Officer)(Signature of person authorized to sign)
8. NAME AND ADDRESS OF CONTRACTOR (No., Street, County, State and Zip Code) X HQ003419R0085
X 9B. DATED (SEE ITEM 11)
17-May-2019
10B. DATED (SEE ITEM 13)
9A. AMENDMENT OF SOLICITATION NO.
11. THIS ITEM ONLY APPLIES TO AMENDMENTS OF SOLICITATIONS
X The above numbered solicitation is amended as set forth in Item 14. The hour and date specified for receipt of Offer is extended, X is not extended.
Offer must acknowledge receipt of this amendment prior to the hour and date specified in the solicitation or as amended by one of the following methods:
(a) By completing Items 8 and 15, and returning 1 copies of the amendment; (b) By acknowledging receipt of this amendment on each copy of the offer submitted;
or (c) By separate letter or telegram which includes a reference to the solicitation and amendment numbers. FAILURE OF YOUR ACKNOWLEDGMENT TO BE RECEIVED AT THE PLACE DESIGNATED FOR THE RECEIPT OF OFFERS PRIOR TO THE HOUR AND DATE SPECIFIED MAY RESULT IN REJECTION OF YOUR OFFER. If by virtue of this amendment you desire to change an offer already submitted, such change may be made by telegram or letter, provided each telegram or letter makes reference to the solicitation and this amendment, and is received prior to the opening hour and date specified.
12. ACCOUNTING AND APPROPRIATION DATA (If required)
13. THIS ITEM APPLIES ONLY TO MODIFICATIONS OF CONTRACTS/ORDERS.
IT MODIFIES THE CONTRACT/ORDER NO. AS DESCRIBED IN ITEM 14.
A. THIS CHANGE ORDER IS ISSUED PURSUANT TO: (Specify authority) THE CHANGES SET FORTH IN ITEM 14 ARE MADE IN THE
CONTRACT ORDER NO. IN ITEM 10A.
B. THE ABOVE NUMBERED CONTRACT/ORDER IS MODIFIED TO REFLECT THE ADMINISTRATIVE CHANGES (such as changes in paying office, appropriation date, etc.) SET FORTH IN ITEM 14, PURSUANT TO THE AUTHORITY OF FAR 43.103(B).
C. THIS SUPPLEMENTAL AGREEMENT IS ENTERED INTO PURSUANT TO AUTHORITY OF:
D. OTHER (Specify type of modification and authority)
E. IMPORTANT: Contractor is not, is required to sign this document and return copies to the issuing office.
14. DESCRIPTION OF AMENDMENT/MODIFICATION (Organized by UCF section headings, including solicitation/contract subject matter where feasible.)
10A. MOD. OF CONTRACT/ORDER NO.
2. AMENDMENT/MODIFICATION NO. 5. PROJECT NO.(If applicable)
6. ISSUED BY
3. EFFECTIVE DATE
24-May-2019
CODE
WHS - ACQUISITION DIRECTORATE
4800 MARK CENTER DRIVE, SUITE 09F09
ALEXANDRIA VA 22350
HQ0034 7. ADMINISTERED BY (If other than item 6)
4. REQUISITION/PURCHASE REQ. NO.
CODE
See Item 6
FACILITY CODECODE
EMAIL:TEL:
HQ003419R0085
SECTION SF 30 BLOCK 14 CONTINUATION PAGE
SUMMARY OF CHANGES
SECTION SF 1449 - CONTINUATION SHEET
The following have been modified:
PWS
PERFORMANCE WORK STATEMENT (PWS)
Office of the Chief Management Officer Data Mining Software-as-a-Service Platform with Data and Analytics Solutions
General Information
1. GENERAL: This is a non-personal services contract to provide data licenses, software licenses, and advisory services. The Government shall not exercise any supervision or control over the contract service providers performing the services herein. Such contract service providers shall be accountable solely to the Contractor who, in turn is responsible to the Government.
1.1 Description of Services/Introduction: The contractor shall provide all personnel, equipment, supplies, facilities, transportation, tools, materials, supervision, and other items and non-personal services necessary to perform all work and services as defined in this Performance Work Statement except for those items specified as government furnished property and services. The contractor shall perform to the standards in this contract.
1.2 Background: The Chief Management Officer (CMO) is the principal Department of Defense (DoD) official responsible to the Secretary and Deputy Secretary of Defense for leading and enabling the management, integration, and improvement of the DoD’s business operations. The Office of the CMO (OCMO) is responsible for working across the Department to break down organizational stovepipes and create a cross-functional, end-to-end business environment that is synchronized to rapidly respond to warfighter needs in the most cost-effective way possible. Working across all DoD components, the OCMO is focused on delivering agile, efficient, and effective business operations that support the warfighter.
The OCMO accomplishes its mission through a series of data-enabled core service offerings, such as business strategic planning, performance management, implementation and oversight of defense business systems, portfolio and investment management, process optimization, architecture and standards development, and the analytics to support all of it. With these service offerings, the OCMO is putting in place a comprehensive data analysis framework for more effective management utilizing the key levers of strategy, people, process, data science, technology, and controls.
This data analysis framework will enable a data science/data-first approach that supports, at scale, current and future reform efforts that enable the National Defense Strategy and provide on-demand and accurate decision-grade information to leaders across the defense enterprise. To reduce cost, increase speed, and improve performance, the OCMO is subscribing to a web-based data-mining SaaS platform with attendant data delivery and data analysis services.
The ID/IQ contract will serve as a consolidated contract vehicle to license the SaaS platform, data to sustain current reform efforts, and procure the analytic capabilities needed to support the OCMO and DoD’s business operations.
1.3 Objectives:
The overarching objective of this support is to provide OCMO and DoD leaders, operators, and analysts the technology and analytical support they need to enable the National Defense Strategy by building a more lethal force and reforming the DoD for greater performance and affordability. The National Defense Business Operations Plan requires ongoing analysis of various DoD lines of business and areas of focus, such as: human resource management; financial management; real property management; logistics and supply chain management; healthcare management; community services; cyber defense and information technology management, and testing and evaluation. Additionally, a data-first approach, at scale, is required to perform analysis across the spectrum of strategic intent, budgeting, spending, and outcomes to optimize business operations in support of the National Defense Strategy.
1.4 Scope: The scope of work is for OCMO headquarters and its Directorates but may extend across all DoD components, including OSD, defense agencies, the Services, and the Joint Force. In support of this mission, OCMO requires a business intelligence firm that can provide an at-scale data-mining Software-as-a-Service (SaaS) platform with direct data access via licensing and expert data analytic services. This includes, but is not limited to:
• Provide a SaaS platform to enable real-time data analysis across the DoD.
• Provide licensed data that must have metadata that enables linkages between currently siloed
DoD systems, e.g., the ability to crosswalk between databases of financial transactions and contracting (and other) data.
• Provide data analysis services that:
o Identify and analyze efficiency opportunities to improve DoD’s affordability and the effectiveness of management support functions across the Office of the Secretary of Defense (OSD) and DoD in support of the National Defense Strategy.
o Perform functional portfolio analysis of DoD investments to determine actual business cost, opportunities for savings, and return on investment (ROI).
o Analyze outcomes, performance measures, and activities across lines of business o Contribute to the execution of DoD enterprise initiatives across the core business processes of the DoD.
o Can be quantified and substantiated to Senior DoD leadership using statistical analysis in conjunction with historical data referenced from the DRCED environment o Resulting models and analytical results can be evaluated and compared using structured quality review process
1.5 Period of Performance: The period of performance shall be for one (1) Base Period of 12 months and four (4) 12-month option periods. The Period of Performance reads as follows:
Base Period: 12 months from date of award Option Period One: 12 months Option Period Two: 12 months Option Period Three: 12 months
Option Period Four: 12 months
1.6 General Information:
1.6.1 Quality Control: The contractor shall develop and maintain an effective quality control program to ensure services are performed in accordance with this PWS. The contractor shall develop and implement procedures to identify, prevent, and ensure non-recurrence of defective services. The contractor’s quality control program is the means by which he assures himself that his work complies with the requirement of the contract. The QCP shall be delivered via electronic mail within 30 days of contract award.
Amendments/changes to the QCP shall be delivered to the COR and KO within three business days following any change. The QCP shall be completed at the IDIQ level.
1.6.2 Quality Assurance: The government shall evaluate the contractor’s performance under this contract in accordance with the Quality Assurance Surveillance Plan. This plan is primarily focused on what the Government must do to ensure that the contractor has performed in accordance with the performance standards. It defines how the performance standards will be applied, the frequency of surveillance, and the minimum acceptable defect rate(s). The QASP shall be maintained at the IDIQ level.
1.6.3 Recognized Holidays: The contractor is not required to perform service on holidays New Year’s Day Labor Day Martin Luther King Jr.’s Birthday Columbus Day President’s Day Veteran’s Day Memorial Day Thanksgiving Day Independence Day Christmas Day
1.6.4 Hours of Operation: The contractor will perform the majority of the services at the contractor site.
However, Government offices will be available for conducting business between the core hours of 8:00am to 4:30pm. Government offices will be closed for Federal holidays or when the Government facility is closed due to local or national emergencies, administrative closings, or similar Government directed facility closings.
1.6.5 Place of Performance: Majority of the performance will be at the contractor site. However, there may be minimal times when the contractor is required to be in the office to complete tasks of retrieving data, meetings, etc. CMO office space is located at both the Pentagon and at the Mark Center, Alexandria, Virginia. The Government does not have any permanent working space for contractors. The government will have hotel cubes for contractor use when necessary. Contractors will have to work from contractor-designated facilities on a permanent basis.
The Place of Performance will be specified at the Task Order level. The infrastructure in place at the contractor site must adequately support daily interaction with Government project leads and team members via telephone or network communication protocols.
The Government will authorize Contractor personnel at Pentagon or other facility building pass, as well as a Common Access Card (CAC) to access required IT systems prior to conducting work on this contract. Contractor personnel must also read and familiarize themselves with all organizational mission statements and charters, organizational structures, operating instructions, Standing Operating Procedures (SOP) and policy.
1.6.6 Type of Contract: The government will award a single-award, Indefinite-Delivery, Indefinite- Quantity contract with firm fixed price task orders.
1.6.7 Security Requirements: A DD Form 254 will be provided as required to the Contractor upon award of a task order.. The Contractor shall comply with all security policies and procedures that apply to DoD and WHS Enterprise Management Directorate (WHS/EM). Security procedures shall be made available to Contractor personnel. It is anticipated that a SECRET facility clearance may be needed for future task orders.
1.6.7.1 Physical Security: If provided, the contractor shall be responsible for safeguarding all government equipment, information and property provided for contractor use. At the close of each work period, government facilities, equipment, and materials shall be secured.
If provided, the Contractor shall establish and implement methods of making sure all keys/key cards issued to the Contractor by the Government are not lost or misplaced and are not used by unauthorized persons. NOTE: All references to keys include key cards. No keys issued to the Contractor by the Government shall be duplicated. The Contractor shall develop procedures covering key control that shall be included in the Quality Control Plan. Such procedures shall include turn-in of any issued keys by personnel who no longer require access to locked areas. The Contractor shall immediately report any occurrences of lost or duplicate keys/key cards to the Contracting Officer.
1.6.7.2.1. In the event keys, other than master keys, are lost or duplicated, the Contractor shall, upon direction of the Contracting Officer, re-key or replace the affected lock or locks; however, the Government, at its option, may replace the affected lock or locks or perform re-keying. When the replacement of locks or re-keying is performed by the Government, the total cost of re-keying or the replacement of the lock or locks shall be deducted from the monthly payment due the Contractor. In the event a master key is lost or duplicated, all locks and keys for that system shall be replaced by the Government and the total cost deducted from the monthly payment due the Contractor.
1.6.7.2.2. If provided, the Contractor shall prohibit the use of Government issued keys/key cards by any persons other than the Contractor’s employees. The Contractor shall prohibit the opening of locked areas by Contractor employees to permit entrance of persons other than Contractor employees engaged in the performance of assigned work in those areas, or personnel authorized entrance by the Contracting Officer.
If provided, the Contractor shall establish and implement methods of ensuring that all lock combinations are not revealed to unauthorized persons. The Contractor shall ensure that lock combinations are changed when personnel having access to the combinations no longer have a need to know such combinations.
These procedures shall be included in the Contractor’s Quality Control Plan.
1.6.8 Special Qualifications: Contractor personnel will be required to sign a Non-Disclosure Agreement.
1.6.9 Post-Award Conference/Periodic Progress Meetings: The Contractor agrees to attend any post-award conference convened by the contracting activity or contract administration office in accordance with Federal Acquisition Regulation Subpart 42.5. The contracting officer, Contracting Officers Representative (COR), and other Government personnel, as appropriate, may meet periodically with the contractor to review the contractor's performance. At these meetings the contracting officer will apprise the contractor of how the government views the contractor's performance and the contractor will apprise the Government of problems, if any, being experienced. Appropriate action shall be taken to resolve outstanding issues. These meetings shall be at no additional cost to the government.
1.6.10 Contracting Officer Representative (COR): The (COR) will be identified by separate letter. The COR monitors all technical aspects of the contract and assists in contract administration. The COR is authorized to perform the following functions: assure that the Contractor performs the technical requirements of the contract: perform inspections necessary in connection with contract performance:
maintain written and oral communications with the Contractor concerning technical aspects of the contract: issue written interpretations of technical requirements, including Government drawings, designs, specifications: monitor Contractor's performance and notifies both the Contracting Officer and Contractor of any deficiencies; coordinate availability of government furnished property, and provide site entry of Contractor personnel. A letter of designation issued to the COR, a copy of which is sent to the Contractor, states the responsibilities and limitations of the COR, especially with regard to changes in cost or price, estimates or changes in delivery dates. The COR is not authorized to change any of the terms and conditions of the resulting order.
1.6.11 Key Personnel: The personnel listed below are considered essential to the work being performed under this contract. Before removing, replacing, or diverting any of the listed or specified personnel or facilities, the Contractor shall (1) notify the Contracting Officer reasonably in advance and (2) submit justification (including proposed substitutions) in sufficient detail to permit evaluation of the impact on this contract. The Contractor shall make no diversion without the Contracting Officer's written consent;
provided that the Contracting Officer may ratify in writing the proposed change, and that ratification shall constitute the Contracting Officer's consent required by this document.
ID/IQ Program Manager
Education/Experience: Shall have a Bachelor's degree in business, economics, international affairs, data analytics, computer science, or a similar degree, with a Masters degree preferred, and twelve (12) years of experience leading engagements with the DoD, four (4) of which must include DoD data analytics and software deployment.
Functional Description: Shall be the contractor's authorized interface with the Government Contracting Officer (CO), the Contracting Officer's Representative (COR), government management personnel and customer agency representatives. Responsible for formulating and enforcing work standards, assigning contractor schedules, reviewing work discrepancies, supervising assigned contractor personnel and communicating policies, purposes, and goals of the organization to subordinates. Shall be responsible for the overall contract performance and shall support project execution activities.
1.6.12 Identification of Contractor Employees: All contract personnel attending meetings, answering Government telephones, and working in other situations where their contractor status is not obvious to third parties are required to identify themselves as such to avoid creating an impression in the minds of members of the public that they are Government officials. They must also ensure that all documents or reports produced by contractors are suitably marked as contractor products or that contractor participation is appropriately disclosed. Contractor personnel will be required to obtain, use, and display a Common Access Card in the performance of this service.
1.6.13 Contractor Travel: Travel will be authorized by the Government on a case-by-case basis according to the Joint Federal Travel Regulations (JFTR).
1.6.14 Other Direct Costs: This category includes, reproduction, and shipping expenses associated with contracted activities and visits to contractor facilities. ODC may also cover certain labor costs, licenses, and other costs approved by the contracting officer or contracting officer’s representative.
1.6.15 Data Rights: As provided by relevant sections of DFARS 252.227 cited below, a range of Data Rights for technical data and computer software fall generally into eight licensing rights categories each reflecting the extent to which the DoD acquires a license to use, release, or disclose that technical data or computer software to persons who are not Government employees or for use by other departments of the
DoD. These eight licensing rights categories are based on whether the technical data is commercial or noncommercial and the extent to which the DoD and/or Contractor provided funding for the technical data or computer software.
In circumstances where an item, component or data is delivered at private expense, the Contractor shall retain proprietary rights (i.e., specifically negotiated license rights in technical data or delivering data with limited rights) and the DoD shall license for a term its use from the Contractor based on the funding of the technical data or computer software. This breakout or segregation of data, items, components or processes developed at private expense will be licensed by the Contractor to the DoD at the practical sub-item level or segregable portion of the process as appropriate. Based on the commercial nature and funding source, licensing by the Contractor to the DoD shall be negotiated as provided under DFARS 252.227-7013, 7014, 7015, 7016, 7017, 7019, 7028, or 7037.
All data development paid for by the Government will be owned by the Government.
For commercial software and data licenses acquired under this contract, the following DFARS sections shall apply: 252.227-7013, 7014, 7015, 7016, 7017, 7019, 7028, or 7037. Contractor shall retain proprietary rights to software and data developed at private expense, and such items will be available to the DOD for licensing on a term basis.
In keeping with 10 US Code § 2377, DoD will seek to acquire commercial items that meet the requirements stated in this document to the extent practicable, for both software and data capabilities.
1.6.16 Organizational Conflict of Interest: Contractor and subcontractor personnel performing work under this contract may receive, have access to or participate in the development of proprietary or source selection information (e.g., cost or pricing information, budget information or analyses, specifications or work statements, etc.) or perform evaluation services which may create a current or subsequent Organizational Conflict of Interests (OCI) as defined in FAR Subpart 9.5. The Contractor shall notify the Contracting Officer immediately whenever it becomes aware that such access or participation may result in any actual or potential OCI and shall promptly submit a plan to the Contracting Officer to avoid or mitigate any such OCI. The Contractor’s mitigation plan will be determined to be acceptable solely at the discretion of the Contracting Officer and in the event the Contracting Officer unilaterally determines that any such OCI cannot be satisfactorily avoided or mitigated, the Contracting Officer may effect other remedies as he or she deems necessary, including prohibiting the Contractor from participation in subsequent contracted requirements which may be affected by the OCI.
1.6.17 Financial Management
Billing for invoices/cost vouchers, as applicable will be addressed at the task order level. Invoices/cost vouchers shall be submitted and processed in Wide Area Work Flow (WAWF) in accordance with DFARS Clause 252.232-7006. Invoices shall conform to the requirements stated in each task order..
Additionally, the following requirements apply:
• Invoices for SaaS platform subscriptions shall be for an annual amount.
• Invoices for data licenses shall be for an annual amount.
• Invoices for data analytics services shall be input into Wide Area Workflow (WAWF) by the 15th of the month for work agreed to by the COR and contractor based on the type and scope of analysis to be performed.
PART 2
DEFINITIONS & ACRONYMS
2. DEFINITIONS AND ACRONYMS:
2.1. DEFINITIONS:
2.1.1. CONTRACTOR. A supplier or vendor awarded a contract to provide specific supplies or service to the government. The term used in this contract refers to the prime.
2.1.2. CONTRACTING OFFICER. 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.
2.1.3. 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.
2.1.4. DEFECTIVE SERVICE. A service output that does not meet the standard of performance associated with the Performance Work Statement.
2.1.5. DELIVERABLE. Anything that can be physically delivered, but may include non-manufactured things such as meeting minutes or reports.
2.1.6. 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.
2.1.7. PHYSICAL SECURITY. Actions that prevent the loss or damage of Government property.
2.1.8. QUALITY ASSURANCE. The government procedures to verify that services being performed by the Contractor are performed according to acceptable standards.
2.1.9. QUALITY ASSURANCE Surveillance Plan (QASP). An organized written document specifying the surveillance methodology to be used for surveillance of contractor performance.
2.1.10. QUALITY CONTROL. All necessary measures taken by the Contractor to assure that the quality of an end product or service shall meet contract requirements.
2.1.11. SUBCONTRACTOR. One that enters into a contract with a prime contractor. The Government does not have privity of contract with the subcontractor.
2.1.12. WORK DAY. The number of hours per day the Contractor provides services in accordance with the contract.
2.1.12. WORK WEEK. Monday through Friday, unless specified otherwise.
2.2. ACRONYMS:
ACOR Alternate Contracting Officer's Representative BCTF Boards, Commissions, and Task Forces CFR Code of Federal Regulations CONUS Continental United States (excludes Alaska and Hawaii) COR Contracting Officer Representative COTR Contracting Officer's Technical Representative COTS Commercial-Off-the-Shelf DD Form 254 Department of Defense Contract Security Requirement List DFARS Defense Federal Acquisition Regulation Supplement DMDC Defense Manpower Data Center DOD Department of Defense EM Enterprise Management Directorate FAR Federal Acquisition Regulation HIPAA Health Insurance Portability and Accountability Act of 1996 KO Contracting Officer OCI Organizational Conflict of Interest OCONUS Outside Continental United States (includes Alaska and Hawaii) ODC Other Direct Costs PIPO Phase In/Phase Out POC Point of Contact PRS Performance Requirements Summary PWS Performance Work Statement QA Quality Assurance QAP Quality Assurance Program QASP Quality Assurance Surveillance Plan QC Quality Control QCP Quality Control Program TE Technical Exhibit WHS Washington Headquarters Services
PART 3
GOVERNMENT FURNISHED PROPERTY, EQUIPMENT, AND SERVICES
3. GOVERNMENT FURNISHED ITEMS AND SERVICES:
3.1. Services: If required, the government will provide basic services to phones and information technology.
3.2 Facilities: If required, basic facilities such as work space and utilities will be provided while working in Government facilities.
3.3 Equipment: If required, the Government will provide phones, desks, and general office supplies while working in Government facilities.
PART 4
CONTRACTOR FURNISHED ITEMS AND SERVICES
4. CONTRACTOR FURNISHED ITEMS AND RESPONSIBILITIES:
4.1 General: If required, the Contractor shall furnish all supplies, equipment, facilities and services required to perform work under this contract that are not listed under Section 3 of this PWS.
4.2 Secret Facility Clearance: The DD 254 as required will be forwarded to the contractor upon award of the task order.
4.3. Materials: NA
4.4. Equipment: NA
PART 5
SPECIFIC TASKS
5. SPECIFIC TASKS:
5.1 Software-as-a-Service (SaaS) Platform General Requirements
5.1.1 Contractor must provide a standardized, normalized, curated, and longitudinally accurate group of DoD-relevant datasets already integrated and available in a mature web-based Software-as-a-Service (SaaS) platform for data analysis. The platform and the analyses derived from it should provide decision-grade information to the DoD to support comprehensive, taxonomic analyses of the defense enterprise. At a minimum, contractor data sets should link, not just contain, budget, contracting, grants, and spending data, and must be able to ingest and link together DoD data sets (internal DoD data) with contractor data sets (data from outside resources) to create a clear view of the government, industry, university, and research center/laboratory landscape, forming the foundation upon which more advanced analysis may be rapidly implemented. The Contractor can use an existing stack for data mining like Microsoft PowerBI and SQL as long as it meets the requirements of this PWS.
5.1.2 The SaaS application shall be the sole property of the contractor and use advanced data science techniques and technologies such as entity extraction, concept search and text analysis, and the ability to detect common semantic relationships between and among data sources that update and refresh, at least daily, for a near real-time picture of DoD business operations.
5.2 Software-as-a-Service Platform Technical Requirements
Contractor will provide a platform with data from outside resources but may also be required to use DoD data to analyze and provide information as required. The prime contractor’s platform shall be able to perform all of the following functions.
5.2.1 Platform Access
5.2.1.1 SaaS platform solution should provide the Government with individual, end-user access to view data from automated, data-science generated analytic frameworks for evaluating federal and commercial marketplace views.
5.2.1.2 SaaS platform solution should provide Application Program Interface (API) access to metadata, complete constructed datasets, or files and transactions.
5.2.2 Scalability and Hosting
5.2.2.1 Solution must be offered in the cloud as software-as-a-service.
5.2.2.2 Solution should be horizontally scalable, allowing additional user scale, data scale, data complexity, and compute complexity.
5.2.2.3 Solution must deliver 99.99% system uptime independent of scheduled maintenance windows.
5.2.2.4 Solution must incorporate automated backup and disaster recovery.
5.2.2.5 Solution must have distributed data storage via cloud that provides a central location for raw access (input or output).
5.2.2.6 Solution must use a flexible schema or schemaless model for storing arbitrary datasets.
5.2.3 Security and Administration
5.2.3.1 Data in transit from client-to-server or server-to-server must be end-to-end encrypted (via SSL/TLS).
5.2.3.2 Cryptographic secrets must be securely managed.
5.2.3.3 Network must permit only a limited number of gateway servers, limiting the number of potential vectors that could compromise one or more hosts.
5.2.3.4 Administrators must have access to a standardized filesystem layout, allowing them to easily find service information and logs.
5.2.4 User Interface
5.2.4.1. Intuitive access to virtually all services of the solution must be achievable through a modern web browser.
5.2.4.2 Components that facilitate easy use by both technical and non-technical analysts alike are requisite as part of the solution.
5.2.4.3 Interactive data visualization is a necessary component of the solution.
5.2.5 Search and Exploration
5.2.5.1 Solution should incorporate artificial intelligence-driven concept recommendations that allow users to build and expand searches without deep subject matter knowledge.
5.2.5.2 Solution’s search interface should return analytics rather than transactions as a basis for exploration and discovery.
5.2.5.3 Solution should incorporate robust advanced search capabilities that support multiple combinations of parameters, hierarchies and keywords.
5.2.5.4 Solution must have the ability to save concept searches and other analytic frameworks that are continuously updated with data and without direct user interaction.
5.2.6 Analytics
5.2.6.1 Solution must natively analyze and link datasets through a taxonomic interface.
5.2.6.2 Solution must visualize data and derivative taxonomies in real-time, allowing for more complex questions to be asked and deeper meaning to be uncovered.
5.2.6.3 Platform must have a minimum of six analytic suites, including: a summary market overview, contract analysis, budget analysis, agency analysis, contractor analysis (including sub-contractors), and document analysis. Each suite must facilitate data filtering over time.
5.2.6.4 Solution must support analytics that integrate DoD data with contractor data set as referenced in 5.1.1.
5.2.6.5 Solution must allow for the export of DoD-defined data sets for use in applications external to the Data Mining SaaS platform.
5.2.7 Data Export
5.2.7.1 Software must allow for data export in multiple formats, including .csv and PDF.
5.2.7.2 Both text and images must be exportable.
5.2.7.3 Users must be able to define parameters of export.
5.2.8 Collaboration
5.2.8.1 Software must enable collaboration among users.
5.3 Data Analysis Services
The contractor shall provide personnel who have the expertise and experience to provide support for the following tasks.
5.3.1 The contractor shall provide data scientists and analysts with knowledge and understanding of their SaaS platform, data, and requirements. Analysts shall provide analyses based on requirements and priorities from demand signals identified by DoD Senior leaders across the Lines of Business of the Department.
5.3.3 The contractorshall support analysis of various lines of business such as real property, healthcare, financial services, and cost accounting analyses to assist the DoD in meeting its overall reform goals.
Existing line of business performance metrics will be provided.
5.3.4 The contractor shall perform specialized analysis to identify redundancies in DoD spending, across multiple portfolios, to identify inefficiencies and increase DoD buying power, among other analyses.
5.3.5 The contractor shall perform analyses to rationalize various DoD investment portfolios, including, but not limited to, its modernization and RDT&E efforts.
5.3.6 The contractorshall identify opportunities to consolidate common functions across contracts within DoD to create economies of scale and efficiencies in services provided by DoD suppliers.
5.3.7 The contractor shall perform analyses to measure successful implementation of the 2018 National Defense Strategy priorities, with data-supported evidence that correlates strategic intent to budget actions, spending and execution, and desired outcomes.
5.4 Data Integration and Curation Requirements
5.4.1 The contractor shall provide a standardized, normalized, curated, and longitudinally accurate group of relevant government and contractor datasets (5.1.1) that are already integrated and available via a mature web-based Software-as-a-Service (SaaS) platform, and include no less than ten years of historical base data, must be part of the solution. The platform and the analyses derived from it should provide decision-grade information to the DoD to support comprehensive, taxonomic analyses of the defense enterprise. The timeframe will be designated for each task order.
5.4.2 The contractor shall provide data that must be linked to various DoD data sources in order to create a clear view of the government, industry, university, and research center landscape, forming the foundation upon which more advanced analysis may be rapidly implemented. The DoD data sources to which the contractor links its data shall include but not limited to contracting, grants and spending data.
5.4.3 The contractor shall use advanced data science techniques and technologies such as data standardization, normalization, entity extraction, concept search text analysis, and forecasting with the ability to detect common semantic relationships between and among data sources that update and refresh daily all performed analyses as new information becomes available.
5.4.4 Based on a set of primary keys, the contractor shall provided linked data to be ingested into DoD systems and organized and analyzed in pre-configured or user-defined taxonomies as required.
5.4.5 Contractor’s SaaS platform must be able to integrate Government-provided data with Contractor data sets (5.1.1) that enables linkages between currently siloed DoD systems, e.g., the ability to crosswalk between databases of financial transactions and contracting (and other) data to enrich advanced analyses to create clear views of Government activity.
5.4.6 If required to access classified data, contractor will be required to comply with all applicable laws, policies and regulations for protecting sensitive data sets. These laws, policies, and regulations will be identified by the Government.
PART 6
APPLICABLE PUBLICATIONS
6. APPLICABLE PUBLICATIONS:
6.1. The Contractor must abide by all statutes, applicable regulations, publications, manuals, and federal policies, procedures identified in the contract.
PART 7
ATTACHMENT/TECHNICAL EXHIBIT LISTING
7. ATTACHMENT/TECHNICAL EXHIBIT LIST:
7.1. Attachment 1/Technical Exhibit 1 – Performance Requirements Summary
7.2. Attachment 2/Technical Exhibit 2 – Deliverables Schedule
TECHNICAL EXHIBIT 1
Performance Requirements Summary
The contractor service requirements are summarized into performance objectives that relate directly to mission essential items. The performance threshold briefly describes the minimum acceptable levels of service required for each requirement. These thresholds are critical to mission success.
Performance Objective (The Service required—usually a shall statement)
Standard PERFORMANCE
THRESHOLD (THIS IS
THE MAXIMUM ERROR
RATE. IT COULD
POSSIBLY BE “ZERO
DEVIATION FROM
STANDARD”)
Method of Surveillance
PRS # 1.
Timeliness of Deliverables required by the Contract
Deliverables shall be submitted in accordance with the delivery requirements required by the PWS.
95% of the deliverables/reports are submitted on time per the timelines designated in Section 7 (Deliverables Schedule) of this contract
COR
TRACKING
PRS # 2
Accuracy of Deliverables required by the contract
Reports and Other Deliverables are complete and correct when submitted.
No more than 3 Errors in content per Deliverable
COR Review for completion and accuracy
PRS # 3 Overall Management of Tasks
Coordinate project activities and provide overall expertise for successful management and completion of each project area.
Project Areas meet all requirements. Problems encountered are minor and resolved in a satisfactory manner.
Customer input/random sampling/ COR review
PRS # 4 Responsiveness Provide the effective responses to requirements & effective balancing of resources to accomplish work
Meets all requirements.
Problems encountered are minor and resolved in a satisfactory manner.
Customer input/random sampling/ COR review
TECHNICAL EXHIBIT 2
DELIVERABLES SCHEDULE
DELIVERABLE FREQUENCY # OF COPIES MEDIUM/FORMAT SUBMIT TO
Non-Disclosure Agreement
Within five (5) days of contract award one MS Word Delivered to COR via email
Project Outline Within five (5) days of contract award one MS Word, DRCED
Confluence and
JIRA
environments
Delivered to COR via email
Quality Control Plan
Within 30 days of contract award one MS Word, DRCED
Confluence and
JIRA
environments
Delivered to COR via email
Written Monthly Status Report
Last calendar day monthly one MS Word, DRCED
Confluence and
JIRA
environments
Delivered to COR via email
Quarterly Meetings
Quarterly one MS Word Delivered to COR via email
Final Deliverable (written report)
Within ten (10) calendar days of contract end date one MS PowerPoint or MS Word, DRCED
Confluence and
JIRA
environments
Delivered to COR via email
SECTION L
SECTION L: INSTRUCTIONS, CONDITIONS, AND NOTICES TO OFFERORS
This section of the RFP provides guidance and information for preparing proposals, as well as instructions on the format and content of the proposal. The Offeror shall submit a complete proposal including all data and information requested by the RFP. The proposal must be submitted in accordance with all Section L instructions.
Any estimates, examples, or scenarios included in Section L are based on the Government’s projected needs and are used for evaluation purposes only. These estimates do not represent a guarantee for any TOs placed against the resulting contract.
Washington Headquarters Services (WHS) is releasing this solicitation electronically only. This electronic version of the Request for Proposal (RFP) is the official version for this acquisition. No hard copy of this solicitation will be issued. Offerors will be sent any applicable revisions to this solicitation electronically.
Offerors must submit their proposals electronically only. Text and graphics portions of the electronic copies shall be compatible with Microsoft Office Suite 2010 applications. All price information shall be in a separate file from all other Factors. Electronic copy proposals may be used for contract formation, and will be used for evaluation. Compact disks (CD) or any removable media devices will NOT be accepted. Electronic proposals are due by the date and time specified on page one of SF 1449 (RFP).
Information requested within this RFP shall be furnished in writing, shall be prepared under the instructions provided, and shall conform to all aspects of this RFP and its attachments. To aid in evaluation, submitted responses shall be clearly and concisely written, as well as neat, indexed and logically assembled. Each Offeror must submit a response to the solicitation consisting of the items described below. The submission of these items to the Government will constitute the Offeror’s compliance with the terms and conditions of the RFP.
The information requested and the manner of submittal is essential to permit prompt evaluation of all proposals on a fair and uniform basis. Any response in which material information requested is not furnished, or where indirect or incomplete answers or information are provided, may be considered non-compliant for evaluation.
The Government will not pay any expenses incurred by any Offeror for the preparation and submission of a proposal in response to this RFP nor any potential proposal revisions during the period of performance of the subsequent award. Offerors are cautioned to ensure that their proposals are complete, address all requirements, reflect the evaluation factors and are submitted on the most favorable terms to reflect their best response. Offerors are strongly encouraged to be succinct, clear, and concise in writing their proposal.
1. Proposal Contents and Due Date. Offerors shall submit their proposals before the due date and time for this solicitation. Offers shall be RECEIVED by the designated Government point of contacts (POCs) by the date and time specified on page one of SF 1449 (RFP). Any proposal received after the exact time specified for receipt shall be treated as a late submission in accordance with Federal Acquisition Regulation (FAR) 52.215-1. Offerors shall submit their proposals with the subject line “RFP HQ0034-19-R-0085.”
2. Offeror’s Questions. The cut-off date and time for all questions is 12:00pm EST, May 23, 2019. Offerors are requested to e-mail all questions to LaTova Greene at latova.j.greene.civ@mail.mil and Kellie Buck at kellie.e.buck.civ@mail.mil. Responses to all questions will be in the form of a solicitation amendment and electronically sent to all Offerors.
No telephonic requests will be accepted.
3. Proposals submitted in response to this solicitation shall be formatted as follows:
a. Text – Text shall be at least single-spaced, on 8½ x 11 inch paper, with a minimum one-inch margin on all sides. Pages shall be numbered consecutively. Pages submitted over the page limitations stated throughout this document will be removed and not evaluated.
b. Font Size – Print shall be of minimum 12-point font size. Bolding, underlining, and italics may be used to identify topic demarcations or points of emphasis. Graphic presentations, including tables, while not subject to the same font size and spacing requirements, shall have spacing and text that is easily readable.
c. The following introductory information (letter format is acceptable; introductory information page *will not* go toward page limits) is required after the cover page of Volume I of your proposal:
(a) RFP Number & Title,
(b) Name and address of vendor,
(c) Name, telephone number & e-mail address of main point-of-contact,
(d) Name of your contract administration office,
(e) Date of submission,
(f) Name, title and signature of authorized representative; and
(g) CAGE code and DUNS number
(h) TIN and size of business (large or small)
Table of Contents: Offeror shall include a Table of Contents and may also include a Table of Acronyms and/or Table of Figures. This will not go toward page limits.
Electronic Copies. Electronic copies of all proposed information for each volume shall be submitted using Microsoft (MS) Office 2010 (MS Word 2010) or Portable Document Format (PDF) using Adobe Acrobat 9.0. Data submitted in spreadsheet files shall be readable by MS Office 2010 (MS Excel 2010).
All Cost/ Price information shall be in files separate from other Factors.
Acceptance of Terms and Conditions of the RFP Offerors shall include the signed 1449 and all amendments to accept all terms and conditions of the RFP.
Offerors may submit a signed memo in lieu of the missing first page of the original solicitation. The memo must acknowledge the terms and conditions of the solicitation, include Offeror Name (Address and Telephone (box 17 of SF1449), Offeror Representative Name and Title, Date, and Offeror Signature (box 30 of SF1449), as well as signed first page of any amendment(s). This shall be provided with Volume I and will not go towards the overall page count.
Prime/Sub-Contracting Arrangements Teaming arrangements will be accepted ONLY as a Prime/Subcontractor relationship.
Written Proposal.
Proposals shall consist of two volumes. All volumes shall be organized as follows:
Volume I – Basic Contract
Factors Title Page Limit Basic Contract 20 pages (for the entire volume), excludes resume for Program Manager
Factor 1 Technical Approach
Factor 2 Corporate Experience
Factor 3 Management and Staffing Approach
Volume 2 – Price All pricing information shall be addressed ONLY in the Price Volume. If pricing information is included in other volumes, it will result in removal of the entire page from evaluation.
Factors Title Page Limit Basic Contract Factor 4 Price No Page Limit (Excel spreadsheet)
Oral Demonstrations.
Oral demonstrations are required as part of the evaluation criteria. Offerors will be notified, at least seven calendar days prior to the demonstration, of the date, time and location the demonstration will take place.
For planning purposes, all demonstrations will occur at or near the Pentagon. Offerors invited to provide a demonstration will be given 72-hour notice of specific scenarios to be demonstrated for evaluation purposes. The requirements for the oral presentations is stated below:
a) Time Limit – The Offeror’s oral presentation shall not exceed 60 minutes. The Contracting Officer reserves the right to terminate the presentation if it overruns the 60 minute limit.
During the presentation, the Source Selection Evaluation Board (SSEB) members will not interrupt the Offeror to ask questions (except to request the repetition of inaudible words or statements or the explanation of terms that are unknown to them) or otherwise engage the Offeror in any dialogue. A question and answer period will follow and may cover the entire proposal. These questions will not constitute “discussions” as defined in FAR 15.306.
b) Offeror Attendees – A maximum of three (3) presenters will be allowedto present. Offerors should have personnel who have the capability to complete the scenarios and answer any technical questions about their platform.
c) Topics – The specific scenario(s) will be provided at least 72 hours in advance.
d) Presentation Media – Offerors are free to structure their oral presentations using computer-generated media.
4. Paper and Electronic Copies – The Offeror shall provide an electronic copy of any presentation materials for the purpose of demonstration preparation. Please provide the documents to the Contract Specialist, LaTova Greene at latova.j.greene.civ@mail.mil by close of business the day before the presentation date. Offerors shall submit their proposals with the subject line “RFP HQ0034-19-R-0085 Demonstration Scenarios.” Presentation materials are for planning purposes only and will not be evaluated as part of the oral presentation.
e) Scheduling – The oral presentation will be scheduled as soon as practicable after proposal receipt, as arranged with the Offerors by the Contracting Officer or Contract Specialist. The Government reserves the right to reschedule presentations at the sole discretion of the Contracting Officer.
f)…
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 .