Attachment 1_Manufacturing Connected Worker Platform Service_SOO.docx
DOCX document 53 KB Posted
- Attached to
- Manufacturing Connected Worker Platform Service
- Solicitation number
- 25-01-DM-BEP
About this file
This document is a Statement of Objectives (SOO) for a Manufacturing Connected Worker Platform Service contract opportunity from the Bureau of Engraving and Printing (BEP), a component of the Department of the Treasury.
The key objectives of this effort are to implement and maintain a FedRAMP certified cloud-based connected worker software tool that enables efficient mobile access to manufacturing information for BEP employees, create and maintain standardized work instructions and training materials in the platform, and deploy the solution on the Treasury's AWS GovCloud environment. The contract will include software licenses, deployment support, and operations and maintenance services. The period of performance is 12 months with up to four 1-year option periods. The work will be performed at the BEP facilities in Washington, D.C. and Fort Worth, Texas.
BEP is seeking responses to a Request for Information (RFI) to gather industry knowledge and information for project planning purposes. Responses are due by November 15, 2024 and should be submitted to the designated points of contact.
View the file
Other files
| File | Type | Posted |
|---|---|---|
| RFI Q_and_As - Manufacturing Connected Worker Platform Svc v5.pdf | ||
| RFI_Manufacturing Connected Worker Platform Service.docx | DOCX document | |
| Attachment 2_Manufacturing Connected Worker Platform Service_RFI Response Template.xlsx | XLSX spreadsheet |
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
Statement of Objectives
Bureau of Engraving and Printing
Manufacturing Connected Worker Platform Service
October 16, 2024
Table of Contents
| Statement of Objectives | 1 | |
| 1. | Purpose | 1 |
| 2. | Background | 1 |
| 3. | Scope | 2 |
| 3.1 | Period & Place of Performance | 2 |
| 4. | Objectives | 2 |
| 5. | Constraints | 4 |
| 5.1 | Access Control | 5 |
| 5.2 | Authentication | 5 |
| 5.3 | HSPD-12 Personnel Security Clearances | 5 |
| 5.4 | Non-Disclosure Agreements | 6 |
| 5.5 | Accessibility | 6 |
| 5.6 | Data | 7 |
| 5.7 | Confidentiality, Security, and Privacy | 7 |
| 5.8 | Acronyms | 7 |
FAR Subpart 37.6 - Performance-Based Acquisition i
1. Purpose Bureau of Engraving and Printing (BEP) is undertaking an application to develop a manufacturing connected worker platform (MCWP) and related services to improve how BEP employees work in a manufacturing setting curriculum. The MCWP shall be deployable in an Amazon Web Services (AWS) GovCloud environment. The goal is to provide BEP a secure deployment of connected worker platform within the Treasury Cloud (T Cloud) AWS environment.
An automated software solution geared toward manufacturing will improve efficiency in information management and overall help to reduce the learning curve of new employees resulting it faster and more effective job proficiency, while working to maintain standardized work practices to enable adherence to cost-effective production practices. The benefits expected to be achieved from this effort are Cost Savings/Cost Avoidance, Increased Compliance, and Increased Stakeholder Satisfaction.
2. Background The Bureau of Engraving & Printing (Bureau/BEP) is the largest producer of security documents in the United States. The BEP prints billions of Federal Reserve notes for delivery to the Federal Reserve System each year. These notes are produced at the Bureau’s Washington, DC and Fort Worth, Texas manufacturing facilities. In addition to U.S. currency, the BEP produces several other security documents such as materials for Homeland Security, military identification cards, and Immigration and Naturalization certificates.
The Bureau CIO Directorate provides management support for all automated systems required to support the Bureau’s manufacturing operations and the activities that support them. These systems include enterprise-wide financial management, manufacturing, and production support systems, as well as localized systems that relates to or support the Bureau’s operations.
TCloud is a robust, flexible, and secure cloud computing infrastructure managed by the Treasury Office of the Chief Information Officer (OCIO). The platform is hosted in AWS and adds built-in, best-of-breed security, encryption, vulnerability, and continuous monitoring capabilities so customers can focus on delivering services to their users efficiently, without sacrificing security or control.
3. Scope The scope of this project is to conduct research, evaluate, and award a firm-fixed price contract for a manufacturing connected worker platform on the Treasury/BEP network using real data satisfying BEP cybersecurity requirements for BEP employees to enable an accelerated pace to upskill the workforce to face the digital environment efficiently.
· The scope of this effort shall encompass following system requirements:
· Capture knowledge of expert employees with photos and videos.
· Develop work instructions and instructional materials from expert employees in both static and dynamic formats that best suits the material.
· Provide a workflow that allows for control of documented information via - tracking, approvals, and release. This workflow should be compliant to or customizable to meet ISO 9001 documented information requirements.
· Turn existing documents and procedures into training programs or other connected worker platform materials.
· Reduce manual data reporting with ITM, eQMS and MES integrations.
· Provide application and integration support during the life of the contract.
The resulting contract will include software licenses, deployment support and operations of maintenance services for the manufacturing connected worker platform software, content creation, and platform in the Treasury Cloud environment.
3.1 Period & Place of Performance
The period of performance is for 12 months from date of contract award, this contract may be extended for up to four (4) one-year option periods. The location for these efforts is the Bureau of Engraving and Printing, Washington DC Facility, Washington, DC and Fort Worth, Texas.
4. Objectives The strategic objective of this effort is to assist in building a workforce of Today and Tomorrow by conducting research, evaluating, and awarding a more automated knowledge management capture and training system, via a connected worker platform, for BEP employees. The overall goal is to generate and improve accessibility of manufacturing information, with a focus on training, to ensure our banknote quality, employee safety, and enablement of standardized work practices. The BEP is pursuing the following major objectives:
4.1 Implement, monitor, and maintain a FedRamp certified cloud-based connected worker software tool that enables efficient mobile access to manufacturing information at point of use.
· The system shall allow for role or group-based permissions – to allow users to view only the content allowed to them based on their role or group.
· The platform shall run on Treasury Cloud Amazon Web Services (AWS) GovCloud environment.
· Shall be capable of at least 1,000 user licenses.
· The platform shall work with a variety of operating systems, inclusive of mobile operating systems like Android and iOS.
· The platform shall allow for bulk user management, enterprise email support, and enterprise onboarding and implementation package.
· The contractor shall develop and provide virtual and in-person training to assist in implementing and maintaining the tool. Contractor personnel shall be available to perform training on all three shifts, as needed.
· The contractor shall provide help desk support for platform end users. Support hours shall be available on all three shifts – with a minimum of two hours of support on each off shift (total 4) during Evening (15:30-23:00/Eastern) and Midnight Shift (24:00-06:30/Eastern) hours.
· The platform should allow end users to create a customized dashboard or customize the existing platform interface to make information most valuable to them easily accessible. Examples include ability to add/remove widgets, allow for favorites or bookmarks, etc.
· The platform should be capable of integrating with other applications. Ideally the platform should integrate with SuccessFactors HXM Suite (Enterprise Edition) and Salesforce.
4.2 Create and maintain instructions, training materials, and other manufacturing content in a collaborative and controlled manner, with a standardized look and feel.
· The contractor shall provide the qualified personnel necessary to develop and maintain work instructions, training materials, templates, and other manufacturing information in appropriate media formats, to include static (Microsoft Word, Adobe PDF, Images, etc.) and dynamic (animations, video, etc.) content.
· The contractor will be responsible for working with the Office of Currency Manufacturing – DCF, Office of Currency Manufacturing-WCF, Office of Quality Engineering and Management, Office of Quality Operations, Office of Engraving, Office of Production Engineering, and Office of Human Resources - Center for Excellence leadership and staff to plan and develop materials for operations, maintenance, engineering, and quality use.
· The contractors’ personnel shall be able to support collaborating with multiple shifts when necessary for content creation. BEP operations generally run three shifts a day, five days a week.
· The platform shall allow for viewing on both desktop and mobile interfaces like Windows, macOS, Android, and iOS.
· The software shall include the ability to track information change history.
· The software shall include the ability to utilize an approval workflow prior to information being published.
· Information shall be revision controlled.
· Information control shall be able to meet ISO 9001:2015 documented information requirements.
4.3 Treasury Cloud Platform Requirements:
· Access from the Treasury Network.
· FISMA High.
· BEP internal security team will obtain the ATT.
· Target Cloud = AWS.
· No external integrations.
· One environment.
· HA requirements = 3 AZs in one region.
· No SaaS components.
· Supports air gapped deployments and does not require external access for licensing servers or container registries.
5. Constraints This section lists laws, rules, regulations, standards, technology limitations and other constraints that the service and/or service provider must adhere to or work under.
5.1 Access Control
User access to the connected worker platform must be integrated with BEP’s Active Directory and support personal identity verification (PIV) card capability based on the Homeland Security Presidential Directive 12 (HSPD 12), dated August 27, 2004, and entitled “Policy for a Common Identification Standard for Federal Employees and Contractors.”. This includes PIV enabled SSO authentication to the environment deployed in the AWS Cloud.
5.2 Authentication
The manufacturing connected worker platform system shall support authentication using Single Sign On capabilities.
5.3 HSPD-12 Personnel Security Clearances
Acquired services shall comply with the following regulations and requirements:
Homeland Security Presidential Directive-12 requires that all federal entities ensure that all contractors have current and approved security background investigations that are equivalent to investigations performed on federal employees.
5.3.1 Security Requirements
1. Personnel Security Clearance. Contractor and subcontractor employee shall be subject to background investigations, conducted by the BEP Office of Personnel Security, before assigned to perform any BEP work. The Contractor shall furnish the COR with all documents required for the security clearance process for each person who will be authorized to have access to the Bureau, but do not currently have an active security clearance from BEP security office, for work under any resultant contract within five (5) working days after contract award.
1. The BEP reserves the right to deny access to its facilities following adjudicative guidelines set forth in Executive order 10450 and applicable supplemental directive, to any individual about which are as adverse suitability determination is made. Failure to submit the required security packet or to truthfully answer all questions contained in security packets shall constitute grounds for denial of access clearance.
2. The selected Contractor shall not provide access to employees, or subcontractor employees, until the BEP Personnel Security Branch, Office of Security, provides written access clearance. Contractors and subcontractors are responsible for reporting all changes concerning their employees, which may affect the suitability of their employees for access to the BEP or placement in any of these positions including additions, or deletions, to the COR within ten (10) workdays of the occurrence of the change.
3. The COR shall maintain a current listing of access requirements and will provide that information to the Personnel Security Branch, Office of Security, BEP. The Personnel Security Branch will inform the COR of all access denials. Denial of access to the BEP does not preclude employment of the individual concerned, by the Contractor, in any capacity not associated with the contract.
4. BEP shall perform the first background check at no cost to the Contractor. The cost of any subsequent background checks made necessary because of the failure of the first applicant shall be borne by the Contractor.
5.3.2 Cyber Security
All Cyber security work shall be done in conjunction with the BEP Office of Critical Infrastructure and IT Security. The contractor shall comply with all aspects of the BEP and the Department of the Treasury IT security program, and NIST FIPS and Special Publications. NIST documents and guidance are available at http://csrc.nist.gov/publications, Systems developed, delivered, or maintained by the contractor must meet the NIST FIPS 200 minimum security requirements.
5.3.3 Special Provision for Security Clearances and Commencement of Work
1. The COR shall provide the Contractor the required BEP security clearance forms prior to entering BEP.
2. The Contractor shall return completed forms for personnel that are to perform directly under this contract to the COR not later than 10 business days after receipt of the forms. The period of time for background clearances to be completed is estimated to be between 30 to 60 Government business days.
3. The Contractor shall be issued a Notice to Proceed by the Contracting Officer when all proposed personnel have been cleared. Within 24 hours after receipt of the notice to proceed, the Contractor shall coordinate with the COR to schedule appointments to have Building Security Badges made for its personnel. The Contractor shall upon receipt of a notice to proceed from Contracting Officer, commerce work at the beginning of the day shift, not later than 72 hours after receipt of the notice to proceed. Therefore, the Contractor’s transition period shall begin and continue for 45 calendar days thereafter. The period of performance for the contract shall not begin until the first day the Contractor personnel report for work.
5.4 Non-Disclosure Agreements
Standard non-disclosure statements shall be provided as required for system administration personnel who may have access to government data in the course of their duties.
5.5 Accessibility
Requirements for accessibility based on Section 508 of the Rehabilitation Act of 1973 (29 U.S.C. 794d) are determined to be relevant. Information about the Section 508 Electronic and Information Technology (EIT) Accessibility Standards may be obtained via the Web at the following URL: www.Section508.gov . The Government Product/Service Accessibility Template (GPAT) is found at Government Product Accessibility Template (GPAT) | National Institute of Corrections (nicic.gov). Generally accepted inspection and test methods corresponding to the identified Section 508 standards are reflected in the EIT Acceptance Guide found at Overview of Testing Methods for 508 Conformance | Section508.gov.
5.6 Data
All data (e-mail traffic, contact information, calendar contents, etc.) is and shall remain the property of the government. The Contractor shall ensure that the government retains access and download capability of all data for research, investigation, transfer, or migration to other systems.
5.7 Confidentiality, Security, and Privacy
In accordance with the Federal Acquisitions Regulations (FAR) clause 52.239-1, the Contractor shall be responsible for the following privacy and security safeguards:
(a) The Contractor shall not publish or disclose in any manner, without the Contracting Officer’s written consent, the details of any safeguards used by the Contractor under the resulting contract or otherwise provided by or for the government.
(b) To the extent required to carry out a program of inspection to safeguard against threats and hazards to the security, integrity, and confidentiality of any non-public government data collected and stored by the Contractor, the Contractor shall afford the government access to the Contractor’s facilities, installations, technical capabilities, operations, documentation, records, and databases.
(c) If new or unanticipated threats or hazards are discovered by either the government or the Contractor, or if existing safeguards have ceased to function, the discoverer shall immediately bring the situation to the attention of the other party.
(d) The Offeror's solution must comply with the BEP CIO IT Security Procedural Guide.
(e) Work on this project may require or allow contractor personnel access to Privacy Information. Personnel shall adhere to the Privacy Act, Title 5 of the U.S. Code, Section 552a and applicable agency rules and regulations.
| 5.8 | Acronyms |
| Acronyms | |
| Description |
| API |
| Application Programming Interface |
| ATT |
| Authority to Test |
| AWS |
| Amazon Web Services |
| BEP |
| Bureau of Engraving and Printing |
| CIO |
| Chief Information Officer |
| COR |
| Contracting Officer Representative |
| DCF |
| Washington, D.C. Facility |
| EIT |
| Electronic and Information Technology |
| eQMS |
| Electronic Quality Management System????? |
| FAR |
| Federal Acquisition Regulation |
| FISMA |
| Federal Information Security Modernization Act |
| GPTA |
| Government Product/Service Accessibility Template |
| HA |
| High Availability |
| HSPD |
| Homeland Security Presidential Directive |
| IT |
| Information Technology |
| ITM |
| Integrated Talent Management |
| MES |
| Manufacturing Execution System |
| NIST |
| national Institute of Standards and Technology |
| OCIO |
| Office of Chief Information Officer |
| OCM |
| Office of Currency Manufacturing |
| OHR-CE |
| Office of Human Resources - Center for Excellence |
| PIV |
| Personal Identity Verification |
| SMART |
| Specific, Measurable, Achievable, Relevant, and Time-bound |
| SOO |
| Statement of Objectives |
| SP |
| Special Publications |
| SSO |
| Single Sign On |
FAR Subpart 37.6 - Performance-Based Acquisition Page SOO-2
File details come from the government source that posted it. Updated .