Loren Data's SAM Daily™

fbodaily.com
Home Today's SAM Search Archives Numbered Notes CBD Archives Subscribe
FBO DAILY - FEDBIZOPPS ISSUE OF JANUARY 28, 2017 FBO #5545
MODIFICATION

D -- Collaborative Project Workspace (CPW) Contract for the National Geospatial-Intelligence Agency Next NGA West Campus (N2W)

Notice Date
1/26/2017
 
Notice Type
Modification/Amendment
 
NAICS
541511 — Custom Computer Programming Services
 
Contracting Office
Department of the Army, U.S. Army Corps of Engineers, USACE District, Kansas City, Attn: CENWK-CT, 635 Federal Building 60l East 12th Street, Kansas City, Missouri, 64106-2896, United States
 
ZIP Code
64106-2896
 
Solicitation Number
W912DQ-16-R-4005
 
Point of Contact
Hilary M. Winans, Phone: 8163893500, Jay B. Denker, Phone: 8163893934
 
E-Mail Address
hilary.m.winans@usace.army.mil, Jay.B.Denker@usace.army.mil
(hilary.m.winans@usace.army.mil, Jay.B.Denker@usace.army.mil)
 
Small Business Set-Aside
N/A
 
Description
The following is a Sources Sought announcement to seek market research information on businesses with capability of providing the services described in the below Statement of Objectives. This is not a Request for Quote (RFQ) or Request for Proposal (RFP). THIS IS NOT A SOLICITATION FOR PROPOSALS AND NO CONTRACT SHALL BE AWARDED FROM THIS SOURCES SOUGHT. No reimbursement will be made for any costs associated with providing information in response to this sources sought or any follow up information requests. This notice is a market research tool used for planning purposes only to determine the availability of capable contractors able to do the following: Statement of Objectives Collaborative Program Workspace (CPW) in Support of the National Geospatial-Intelligence Agency (NGA) Next NGA West (N2W) Program 1. Program Objective: The U.S. Army Corps of Engineers (USACE) seeks a cloud-based information workspace and service that is highly collaborative with an ability to retain multiple large technical documents and offer accessibility to all team members. The objective of the Collaborative Program Workspace (CPW) is to support information sharing for the planning, design, and construction of a replacement main office building and ancillary support buildings/infrastructure for the National Geospatial-Intelligence Agency's (NGA) site in St. Louis, Missouri. The new project is referred to as the Next NGA West (N2W) Program, and is estimated at approximately $1 Billion for the construction effort. It will be constructed in an urban location within the City of St. Louis, Missouri. USACE will manage the construction efforts on behalf of NGA, but there will be numerous contractors supporting the effort. Teams will work in a highly virtual environment with team members contributing from all over the United States. The cloud-based information sharing system will need to provide a secure and collaborative workspace for progressive information management and sharing. It will need to capture, control, and transfer files throughout the life cycle of the N2W program. Complementing the system, a service will be necessary to assist teams with organizing technical information and preparing a tailored forum where information sharing and decision-making can be easily conducted. The combination of the system and the service needs to be ideal for coordination and communication among various governmental agencies, external partners, contractors, and support team members. 2. Contract Objectives: 2.1. High Performance: The proposed N2W CPW shall be capable of meeting the demand of large applications and documents so that workflows are fast, reliable, collaborative and efficient. Data and documents need to be accepted and retained in their native format and retrieved from the system following project completion. Documents also need revision history for tracking of the iterative process and to clearly identify the most up-to-date version. 2.2. Security and Permissions: All data shall be encrypted both in-flight and at rest (point-to-point). USACE shall have full control over who has access to the data stored and retain all data rights. 2.3. National Availability: All data shall be available in regions throughout the country. 2.4. Fully Managed: The service shall be fully managed including, but not limited to, providing assistance in establishing organizational file structure and conducting training with team members. 2.5. Global Platform: The proposed system shall be accessible from multiple and different types of computers with a preference to not rely on a software install. 2.6. Information Management: The information system and service shall have experience managing large, complex construction projects, and provide suggestions on organizational structure for best management. The management and system and service need to provide the following components: • Provide a program document and data repository • Real time updates and edits in files • Enable multiple users to access the same file from different locations, make edits or comments without creating multiple file versions • Provide virtual workrooms for multiple users with access to multiple files • Allow for variable permission levels (read/access/download vs. write/create/upload) • Facilitate efficient organizational structure of files • File register that tracks all of the files that are in the system • Provide capacity to house large file documents (ex. plans and specifications, construction documents) • Provide 24/7 reliability and access • Offer broad accessibility from multiple locations • Provide dedicated customer support • Be easy to use, with training and help guides in literature and/or video format • Offer scalable phases • Meet USACE requirements for data storage (DISA Level 5 preferred). • Facilitate collaboration • Accept, retain, and allow retrieval of many different types of documents, data, and drawings in their native format • Accessible and useable across many different device platforms (computers, tablets, and smartphones). Preferred accessibility to system without software install. • Allow for the transfer of all the files and data to NGA at the end of the project for their operation & maintenance (O&M) uses 2.7. Examples of data and documents to be stored from design, construction, and operation & maintenance: 2.7.1. Design • Request for Proposal (RFP) development documents • Design Analysis • Edited specifications • Building Information Modeling (BIM) drawings 2.7.2. Construction • Submittals for review and approval along with all comments and responses • Amended plan sheets • Amended specifications • Redline drawings • RFIs and responses • Schedules • Calendars • Status reports • Briefings • Meeting minutes • Agendas • Payroll data • Lessons learned trackers • Deficiency lists • Photos/images • Standard Operating Procedures • Standard forms • Organizational charts • Contact rosters • Start-up and testing checklists 2.7.3. O&M • Manufacturer's information • Start-up and testing reports • Equipment manuals • Training information • As-built drawings and building information models (BIM deliverables) • Compiled O&M manuals 3. Period of Performance: The period of performance will be broken out in accordance with the various stages of the NGA N2W acquisition life-cycle. The Contract Line Item Number (CLIN) structure of this solicitation will reflect the following acquisition stages: 3.1. Planning and Design 3.2. Construction (Separate for each Construction Year) 3.3. Operation and Maintenance (Separate for each O&M Year) 4. Objectives: At a minimum, this SOO supports the following requirements: 4.1. Requirement 1: Provide a secure cloud-based project information system and service to serve as a collaborative forum for progressive information management by capturing, controlling, and transferring files throughout the life cycle of the N2W program. 4.2. Requirement 2: Train users on the system (both initial and for new employees as needed). Users include team members from USACE, NGA, City of St. Louis, Contractor Support (Multiple), and U.S. Air Force. 4.3. Requirement 3: Transfer of ownership of N2W project system to NGA, for their use. 5. Constraints: This section lists laws, rules, regulations, standards, technology limitations, and other constraints that the service and/or service provider shall adhere to or work under. 5.1. The vendor shall provide services within a Department of Defense (DoD) level 5 environment (level 5 preferred, but USACE seeking option of level 4) and comply with applicable DoD instructions, directives, and security guides including the Risk Management Framework (RMF) process. 5.1.1. If providing software as a service (SAAS), the vendor shall be approved or gain approval through DISA. 5.1.2. If the vendor already has a DoD level 5 approved hosting facility, USACE will work with them. (contract dependent) 5.1.3. If no DoD level 5 approved environments are available, is the vendor willing to work within the USACE level 5 cloud environment? 5.1.4. If 5.1-1.3 is not feasible, is the vendor willing to pursue/obtain DoD approval for a DoD level 5 cloud offering/environment IAW the guidelines provided in the references below? 5.2. Personnel Security Clearances: Favorable completion of a National Agency Check (NAC) (current within 180 days). Additional requirements and prohibitions apply to foreign nationals IAW Army Regulation 25-2 Information Assurance. 5.3. 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.4. Accessibility: By various government agencies and contractors, USACE determines who is granted access. Accessibility shall be in accordance with pertinent laws, codes and regulations including but not exclusive to the following: 44 U.S.C chapters 21, 29, 31 and 33; Freedom of Information Act (5 U.S.C. 552); Privacy Act (5 U.S.C. 552a); 36 CFR Part 1222 and Part 1228. 5.5. Deliverables and Records: Contractor shall treat all deliverables under the contract as the property of the U.S. Government for which the Government Agency shall have unlimited rights to use, dispose of, or disclose such data contained therein as it determines to be in the public interest. 5.5.1. Contractor shall not create or maintain any records that are not specifically tied to or authorized by the contract using Government IT equipment and/or Government records. 5.5.2. Contractor shall not retain, use, sell, or disseminate copies of any deliverable that contains information covered by the Privacy Act of 1974 or that which is generally protected by the Freedom of Information Act. 5.5.3. Contractor shall not create or maintain any records containing any Government Agency records that are not specifically tied to or authorized by the contract. 5.5.4. Contractor shall deliver sufficient technical documentation with all data deliverables to permit the agency to use the data. The USACE owns the rights to all data/records, electronic information (electronic data, electronic information systems, electronic databases, etc.) and all supporting documentation created as part of this contract produced as part of this 5.5.5. Contractor agrees to comply with USACE records management policies, including those policies associated with the safeguarding of records covered by the Privacy Act of 1974. These policies include the preservation of all records created or received regardless of format [paper, electronic, etc.] or mode of transmission [e-mail, fax, etc.] or state of completion [draft, final, etc.]. 5.5.6. No disposition of documents will be allowed without the prior written consent of the Contracting Officer. The Agency and its contractors are responsible for preventing the alienation or unauthorized destruction of records, including all forms of mutilation. Willful and unlawful destruction, damage or alienation of Federal records is subject to the fines and penalties imposed by 18 U.S.C. 2701. Records may not be removed from the legal custody of the Agency or destroyed without regard to the provisions of the agency records schedules. 5.6. Additional Contract Support: Contractor is required to obtain the USACE Contracting Officer's approval prior to engaging in any contractual relationship (sub-contractor) in support of this contract requiring the disclosure of information, documentary material and/or records generated under, or relating to, this contract. The Contractor (and any sub-contractor) is required to abide by Government and Agency guidance for protecting sensitive and proprietary information. How to respond to this sources sought notice. If your company has recent experience similar to that mentioned in the above statement of objectives please respond to the information below by email to: Hilary.m.winans@usace.army.mil by 2:00 pm Central Standard Time (CST) Wednesday, February 1, 2017. 1. Provide a description of up to five (5) five similar projects supported by your company as a prime contractor within the past seven (7) years, including as much of the following information as possible: (a) dollar amount of the contract; (b) brief description of the technical requirements of that project; (c) a description of the size, complexity, square footage of the similar project; (d) describe the work that was self-performed; (e) description of the system that your firm provided to support the project and the benefits that this system provided for the designer, constructor, and owner, (f) name, address, point of contact and phone number of customer organization for which the work was done. (g) provide a link, if available, to the company website and any available demonstration of the product used by your firm. 2. Firm's business size and, if applicable, small business category: Large Business, Small Business, (Section 8(a), Historically Underutilized Business Zones (Hub-Zone), Women Owned, Service Disabled Veteran Owned (SDVOSB), etc. 3. Firm's Joint Venture information, if applicable - existing and potential. The response must be specific to the qualifications listed above to show that the respondent meets the requirements and possesses the necessary skills and experience. If a response does not show that the respondent meets the qualifications and/or does not possess the necessary skills and experience, the respondent will not be considered by the Government. Again this is not a request for proposal or quotation; there is no solicitation available at this time. A determination by the Government to proceed with the acquisition as a set-aside for 8(a) program, HUBZone, Small Business, etc. or unrestricted is within the discretion of the Government. 4. Responses to the following questions regarding the software services provided by your company: A. Is the software cloud based or does it require a form of software installed on devices for access? B. How does the registration process work and how is access granted to the system/software? C. Is the system/software useable on a tablet or smartphone? What capabilities do both of these devices have with the system/software? Does the product require software on the desktop? D. Are users allowed to add files to the systems or what is the process to add a file? E. Can notifications be sent out to users and user groups when files are uploaded? F. How are simultaneous edits to a document by multiple users resolved? G. Can files be locked or changed to an uneditable version? H. Is the organization structure locked or can it be customizable to the using group? Can be altered after it has been established/created? I. What is the largest size of file that can be uploaded and what is the typical upload speed? J. Is there any certain file types that are not compatible with the system/software? K. What is the standard maintenance on the system/software (weekly or monthly) and how long is the system impacted? L. What happens to the data at the end of the contract? M. What is the pricing model? I.e. multiple projects? a. Is the pricing model and product scalable for reduction and/or growth based on use? N. What authentication and role based access is used? a. Can the product/services be configured to utilize Public Key Infrastructure? O. Is the vendor currently supporting any federal / DoD agencies? P. Is the vendor categorized as a small business? Q. Does the product have a method to flag certain documentation as critical for significant decision documents, final documents, agreements/commitments between entities, etc.
 
Web Link
FBO.gov Permalink
(https://www.fbo.gov/spg/USA/COE/DACA41/W912DQ-16-R-4005/listing.html)
 
Place of Performance
Address: TBD, United States
 
Record
SN04382315-W 20170128/170126234337-d9b7bea4d16f03b3647b350d4a468ba6 (fbodaily.com)
 
Source
FedBizOpps Link to This Notice
(may not be valid after Archive Date)

FSG Index  |  This Issue's Index  |  Today's FBO Daily Index Page |
ECGrid: EDI VAN Interconnect ECGridOS: EDI Web Services Interconnect API Government Data Publications CBDDisk Subscribers
 Privacy Policy  Jenny in Wanderland!  © 1994-2024, Loren Data Corp.