Loren Data's SAM Daily™

FBO DAILY ISSUE OF NOVEMBER 20, 2010 FBO #3283
MODIFICATION

D -- Amendment No. 1 to the Annoucement A1100000062

Notice Date

11/18/2010
 

Notice Type

Modification/Amendment
 

Contracting Office

DSC-CS Contracting Services Division National Park ServiceP.O. Box 25287 Denver CO 80225
 

ZIP Code

80225
 

Solicitation Number

N2090110015
 

Response Due

12/2/2010
 

Archive Date

11/18/2011
 

Point of Contact

Carmen J. Washington Contract Specialist 3039692307 carmen_washington@nps.gov;
 

E-Mail Address

Point of Contact above, or if none listed, contact the IDEAS EC HELP DESK for assistance
(EC_helpdesk@NBC.GOV)
 

Small Business Set-Aside

Total Small Business
 

Description

Amendment No. 1 - during transmission of the Annoucement an error occurred resulting in an incomplete solicitation. This Amendment No. 1will add the Solution Requirements and the Section 508 Compliance Questions. The completion of these questions and requirement is to be provided with your proposal as outlined in the solicitation. Solution RequirementsThese requirements are ranked in order of importance to the project and some may be implemented at a later time. Requirements listed are rated with a number from 3 to 5. A 5 rating is a requirement that is mandatory. A 4 rating is very important to overall project success, a 3 rating is something that would be nice to have or may be implemented at a later time. NOTE: For each requirement please indicate the current development status of your proposed product. Indicate SPF, SPC, and NPC are mutually exclusive codes, indicate only one code per requirement. If the product cannot comply then no code should be selected. The basic instructions for completing are as follows:"SPF means that the product/solution can meet 100% of the requirement with the as-is COTS product (i.e., it is a Standard Product Feature)."SPC means that the product/solution can meet 100% of the requirement with some minor configuration. The proposal should indicate what configuration would be necessary. (SPC-Standard Product with Configuration)"NPC means that the product/solution can meet 100% of the requirement with some minor customization. The proposal should indicate what customization (and level of effort) would be necessary. NPC-Standard Product with Customization)"For each requirement explain/describe how your product meets the code you selected. See Requirement 1.1 as example.Architecture Requirement #: 1.1- Solution is built on an open and industry standard architecture, Rating: 5Comments: Describe Solution architecture. Describe what development technology is used in your product.(.NET, etc)SPF__NPC__SPC__Vendor Response: Requirement #: 1.2 -Solution provides a comprehensive API or SDK to allow interfacing and integration Rating: 4Comments: Provide information regarding your product APIs that would be available to NPS to extend the product functionality- Requirement #: 1.3- SharePoint farms and sites, Rating: 5Comments: Is there any limit to the number of farms or sites the solution can pull content from SPF__NPC__SPC__Requirement #: 1.4- Support for multiple authentication methods, Rating: 5Comments: Ability to authenticate against SharePoint (NTLM, Kerberos, Claims)Requirement #: 1.5- Support for SharePoint in a hosted environment outside of local NPS network (Microsoft SharePoint Cloud and/or Dept of Interior's Private Cloud), Rating: 5Comments: The Documentum Records Management System is completely inside the NPS firewall currently with no access available via the Internet. The proposed solution must support archiving content and metadata from SharePoint farms that reside outside of the NPS firewall to Documentum. Include any specific information about network architecture requirements (ports used, communication protocols, etc) or changes to the NPS environment to support the proposed solution. Requirement #: 1.6- SSL secured sites, Rating: 5Comments: Ability to connect to https configured SharePoint sitesRequirement #: 1.7- SharePoint content access, Rating: 5Comments: Describe the ways content is accessed in SharePoint (API, web services, SQL, CMIS services)Requirement #: 1.8 - Documentum content access, Rating: 5Comments: NPS currently has a single Documentum Docbase for all NPS Records. Describe the ways content is delivered to the Documentum Docbase (e.g. DFC API, SQL, DQL, CMIS services, other). Requirement #: 1.9, Transactional based, Rating: 5Comments: Does the proposed solution use transactions or some other mechanism to ensure integrity of an archive operation instance?Requirement #: 1.10- Proposed solution throttling, Rating: 3Comments: Does the proposed solution allow for scheduling archive to run during non-peak hours or to reduce network bottlenecks?Requirement #: 1.11- Solution can be scaled to insure performance as content expands, Rating: 5Comments: Explain how your solution scales. NPS anticipates that the number of SharePoint sites will grow beyond 1,500 active sites and size of content will grow to around 5gb a site. If NPS were to implement additional Documentum Content Servers or additional Documentum Docbases in the future, will the archive solution support this?Requirement #: 1.12- Support for wide range of file formats, Rating: 5Comments: Provide a list of supported formatsRequirement #: 1.13- Support for large file sizes, Rating: 5Comments: Describe if your solution has file size limits beyond that of the underlying platformsRequirement #: 1.14 - Compress large files, Rating: 4Comments: Provides the ability to perform file compression during transport.Requirement #: 1.15- Compression method, Rating: 4Comments: Describe compression method usedRequirement #: 1.16- Support for 64 bit, Rating: 5Comments: Proposed solution is compatible with a 64 bit environmentRequirement #: 1.17- Error reporting, Rating: 5Comments: Error reportingRequirement #: 1.18- Provides fault tolerance, load balancing, and high availability, Rating: 4Comments: Integrated into SharePoint central administration site. Load balance across multiple SharePoint WFE. Health Analyzer?Requirement #: 1.19- SharePoint stability, Rating: 5Comments: Describe how your solution does not hinder SharePoint's stability if a failure occurs with the proposed solution?Requirement #: 1.20- SharePoint Server 2010 supported, Rating: 5Requirement #: 1.21- Microsoft Office SharePoint Server 2007 supported, Rating: 4Requirement #: 1.22- Documentum Enterprise Content Management System Version 6.5 SP1 is supported, Rating: 5Comments: Indicate that support includes the following components including the custom object types that are part of these applications: a)Content Server/Docbase,b)Records Management Application (RMA) c)Retention Policy Services Application (RPS) d)Digital Asset Management Applicatione)DFC API f)Document Query Language (DQL)Requirement #: 1.23- Documentum Enterprise Content Management System Version 6.6 is supported, Rating: 5Comments: Indicate that support includes the following components including the custom object types that are part of these applications: a)Content Server/Docbase,b)Records Management Application (RMA) c)Retention Policy Services Application (RPS) d)Digital Asset Management Applicatione)DFC APIf)Document Query Language (DQL)Requirement #: 1.24-File System, Rating: 3Comments: Does your solution support archive content and metadata from the file system?Configuration and FeaturesRequirement #: 2.1- Administration, Rating: 4Comments: Does the solution have a user interface for administration of the archive process?Requirement #: 2.2- Archive rules, Rating: 5Comments: Describe the process to establish the content archiving rules including how to map metadata from SharePoint to Documentum. Also describe how the rules can be reused across several SharePoint sitesRequirement #: 2.3- Archive rule scope, Rating: 4Comments: At what SharePoint scope are these rules created? (farm, site collection, site)Requirement #: 2.4- Ability to schedule archive rules to run, Rating: 5Comments: Archive rule s are configurable to run on a set schedule (ex. Daily, weekly, monthly)Requirement #: 2.5- Ability to run archive rules on an event driven basis, Rating: 5Comments: Archive rules are configurable to run on metadata or workflow based event (ex. Status = 20% milestone)Requirement #: 2.6- Ability to run archive rules on-demand, Rating: 3Comments: Archive rules can be run ad-hoc on demandRequirement #: 2.7- Ability to manually "queue" items to be archived, Rating: 3Comments: Archive rule can be run against content items that have been manually queued by a user for a future archiving runRequirement #: 2.8- Mechanisms available in SharePoint that trigger an archive process, Rating: 5Comments: Is it based on rules that perform a query to find content? Based on some event? Placing content in a folder? Requirement #: 2.9- Connect to multiple SharePoint farms, Rating: 5Comments: Cross site and farm accessibilityRequirement #: 2.10- Support for content and metadata, Rating: 5Comments: Metadata is archived along with content. Ability to map metadata fields from SharePoint to Documentum fields.Requirement #: 2.11- Select individual content items for archiving, Rating: 5Comments: Ability to select individual documents or content based on metadata or state of contentRequirement #: 2.12- Site Scoped metadata, Rating: 4Comments: Ability to map site metadata to item metadata being archived (e.g. all content in a specific site will have a NPS Park Name associated to all the content once it is archived to Documentum). Describe where the site scoped metadata will be stored.Requirement #: 2.13- Archive additional content types, Rating: 4Comments: Content is beyond documents. Support for custom lists, calendars, discussion boards and tasks. Please describe which additional SharePoint content types are supported and which content types are not supportedRequirement #: 2.14- SharePoint list based items, Rating: 4Comments: Describe how list based items are stored in Documentum and how they would be versioned?Requirement #: 2.15- Archive wiki and blog pages, Rating: 4Comments: Support for wiki and blog pagesRequirement #: 2.16- Content transport mechanism, Rating: 5Comments: Describe how content and metadata is transported from SharePoint to Documentum? Include methods and protocols used as well as listing any requirement for shared drives/network storage, etc.Requirement #: 2.17- Archive content, Rating: 3Comments: Describe if any SharePoint or Documentum objects are created as a result of the archive process.Requirement #: 2.18- Archive metadata, Rating: 5Comments: Describe the mechanism used to copy metadata from SharePoint to DocumentumRequirement #: 2.19 - Copy content, Rating: 5Comments: SharePoint content is copied without removing it from the siteRequirement #: 2.20- Move content, Rating: 4Comments: SharePoint content is moved from the site and no longer availableRequirement #: 2.21- Move content and leave a link behind, Rating: 4Comments: SharePoint content is moved from the site and a link or stub is left behind.Requirement #: 2.22- Version control, Rating: 5Comments: Archive must retain version controls and be able to archive all or specific versions of content. Describe the ways it achieves this on both the source (SharePoint) system and target (Documentum) system?Requirement #: 2.23- Resubmit option, Rating: 4Comments: Ability to overwrite archive if version number is the same or error occurs in archiveRequirement #: 2.24- Content Type mapping, Rating: 5Comments: Ability to map SharePoint content types to Documentum object types. Describe the content type mapping options available for 1 to 1, 1 to many and many to 1. Also indicate whether the mappings can be SharePoint Site Specific, based on the archive rule that is defined or any other mechanism that provides flexibility in the solution for NPSRequirement #: 2.25- Automatically initiate Documentum Workflow/Business Processes once content is archived to Documentum, Rating: 3Comments: Describe any ability to initiate workflows or business processes for individual content items or all content archived at a point in time from a specific SharePoint SiteRequirement #: 2.26- SharePoint system metadata objects, Rating: 5Comments: Does the archive solution allow SharePoint system metadata to be copied into Documentum object metadata (e.g. created date, created by, modified by, etc)Requirement #: 2.27- Use of Document Sets in SharePoint 2010, Rating: 3Comments: Document sets are containers in SharePoint to bundle documents together. If so, how would the document sets be represented in Documentum?Requirement #: 2.28- Relationship between SharePoint content and Documentum, Rating: 5Comments: Ability to see relationship between content in SharePoint and archived content in Documentum for reference.Requirement #: 2.29- Archive Report, Rating: 4Comments: View content that will be archived during the next runRequirement #: 2.30- Archive history, Rating: 5Comments: Audit controls to view archive process history (list of content moved during archive set)Installation and LicensingRequirement #: 3.1 SharePoint install footprint, Rating: 5Comments: Describe any requirements for installation in SharePointRequirement #: 3.2- Hosted SharePoint environments, Rating: 5Comments: Does your product work in a hosted environment where access to the servers will be outside the NPS firewall?Requirement #: 3.3- SharePoint Features, Rating: 5Comments: Are there any features that are installed into the SharePoint farm, site collection? (Sandboxed solutions in 2010)Requirement #: 3.4- Documentum install footprint, Rating: 5Comments: Describe any requirements for installation of Documentum software/API's to support the proposed solutionRequirement #: 3.5- Solution runs as a windows service, Rating: 5Comments: Does the archive Solution run as a windows service or part of SharePoint servicesRequirement #: 3.6- License Model, Rating: 5Comments: Explain your license modelRequirement #: 3.7- Deleting Sites, Rating: 5Comments: Does the licensing model allow for creating and deleting sites over time? Requirement #: 3.8- SharePoint licenses, Rating: 5Comments: Does your product affect current SharePoint CALs?Requirement #: 3.9- Documentum licenses, Rating: 5Comments: Does your product affect current Documentum Per User Licensing?Requirement #: 3.10- GSA Contract, Rating: 4Comments: Do you or a reseller currently have a GSA ScheduleSupport RequirementsRequirement #: 4.1- Support Offerings, Rating: 4Comments: Explain the support options for issues and bugs that may arise including1.Contact methods (email, phone), processes, and standard operating procedures2.Estimated call volume, hours of operation, after hours call handling, etc.3.Service level metrics (average speed of answer, response time, etc.)Ticket tracking systemSection 508 RequirementsRequirement #: 5.1- Applications shall not disrupt or disable activated features of other products that are identified as accessibility features, where those features are developed and documented according to industry standards. Applications also shall not disrupt or disable activated features of any operating system that are identified as accessibility features where the application programming interface for those accessibility features has been documented by the manufacturer of the operating system and is available to the product developer.Rating: 3Fully__Partially__No__Don't Know__Requirement #: 5.2- Applications shall not override user selected contrast and color selections and other individual display attributes.Rating: 3Fully__Partially__No__Don't Know__Requirement #: 5.3 - At least one mode of operation and information retrieval that does not require user vision shall be provided, or support for Assistive Technology used by people who are blind or visually impaired shall be provided.Rating: 3Fully__Partially__No__Don't Know__Requirement #: 5.4 - At least one mode of operation and information retrieval that does not require visual acuity greater than 20/70 shall be provided in audio and enlarged print output working together or independently, or support for Assistive Technology used by people who are visually impaired shall be provided.Rating: 3Fully__Partially__No__Don't Know__Requirement #: 5.5- At least one mode of operation and information retrieval that does not require user hearing shall be provided, or support for Assistive Technology used by people who are deaf or hard of hearing shall be provided.Rating: 3Fully__Partially__No__Don't Know__Requirement #: 5.6 - Where audio information is important for the use of a product, at least one mode of operation and information retrieval shall be provided in an enhanced auditory fashion, or support for assistive hearing devices shall be provided.Rating: 3Fully__Partially__No__Don't Know__Requirement #: 5.6- Where audio information is important for the use of a product, at least one mode of operation and information retrieval shall be provided in an enhanced auditory fashion, or support for assistive hearing devices shall be provided.Rating: 3Fully__Partially__No__Don't Know__Requirement #: 5.7 - At least one mode of operation and information retrieval that does not require user speech shall be provided, or support for Assistive Technology used by people with disabilities shall be provided.Rating: 3Fully__Partially__No__Don't Know__Requirement #: 5.8- At least one mode of operation and information retrieval that does not require fine motor control or simultaneous actions and that is operable with limited reach and strength shall be provided.Rating: 3Fully__Partially__No__Don't Know__Requirement #: 5.9 - Product support documentation provided to end-users shall be made available in alternate formats upon request, at no additional charges.Rating: 3Fully__Partially__No__Don't Know__Requirement #: 5.10- Product support documentation provided to end-users shall be made available in alternate formats upon request, at no additional charges.Rating: 3Fully__Partially__No__Don't Know__Requirement #: 5.10- End-users shall have access to a description of the accessibility and compatibility features of products in alternate formats, or alternate methods upon request, at no additional charge.Rating: 3Fully__Partially__No__Don't Know__Requirement #: 5.11- Support services for products shall accommodate the communication needs of end-users with disabilities.Rating: 3Fully__Partially__No__Don't Know__Section 508 RequirementsRequirement #: 5.1- Applications shall not disrupt or disable activated features of other products that are identified as accessibility features, where those features are developed and documented according to industry standards. Applications also shall not disrupt or disable activated features of any operating system that are identified as accessibility features where the application programming interface for those accessibility features has been documented by the manufacturer of the operating system and is available to the product developer.Rating: 3Fully__Partially__No__Don't Know__Requirement #: 5.2- Applications shall not override user selected contrast and color selections and other individual display attributes.Rating: 3Fully__Partially__No__Don't Know__Requirement #: 5.3 - At least one mode of operation and information retrieval that does not require user vision shall be provided, or support for Assistive Technology used by people who are blind or visually impaired shall be provided.Rating: 3Fully__Partially__No__Don't Know__Requirement #: 5.4 - At least one mode of operation and information retrieval that does not require visual acuity greater than 20/70 shall be provided in audio and enlarged print output working together or independently, or support for Assistive Technology used by people who are visually impaired shall be provided.Rating: 3Fully__Partially__No__Don't Know__Requirement #: 5.5- At least one mode of operation and information retrieval that does not require user hearing shall be provided, or support for Assistive Technology used by people who are deaf or hard of hearing shall be provided.Rating: 3Fully__Partially__No__Don't Know__Requirement #: 5.6 - Where audio information is important for the use of a product, at least one mode of operation and information retrieval shall be provided in an enhanced auditory fashion, or support for assistive hearing devices shall be provided.Rating: 3Fully__Partially__No__Don't Know__Requirement #: 5.6- Where audio information is important for the use of a product, at least one mode of operation and information retrieval shall be provided in an enhanced auditory fashion, or support for assistive hearing devices shall be provided.Rating: 3Fully__Partially__No__Don't Know__Requirement #: 5.7 - At least one mode of operation and information retrieval that does not require user speech shall be provided, or support for Assistive Technology used by people with disabilities shall be provided.Rating: 3Fully__Partially__No__Don't Know__Requirement #: 5.8- At least one mode of operation and information retrieval that does not require fine motor control or simultaneous actions and that is operable with limited reach and strength shall be provided.Rating: 3Fully__Partially__No__Don't Know__Requirement #: 5.9 - Product support documentation provided to end-users shall be made available in alternate formats upon request, at no additional charges.Rating: 3Fully__Partially__No__Don't Know__Requirement #: 5.10- Product support documentation provided to end-users shall be made available in alternate formats upon request, at no additional charges.Rating: 3Fully__Partially__No__Don't Know__Requirement #: 5.10- End-users shall have access to a description of the accessibility and compatibility features of products in alternate formats, or alternate methods upon request, at no additional charge.Rating: 3Fully__Partially__No__Don't Know__Requirement #: 5.11- Support services for products shall accommodate the communication needs of end-users with disabilities.Rating: 3Fully__Partially__No__Don't Know__
 

Web Link

FBO.gov Permalink
(https://www.fbo.gov/spg/DOI/NPS/APC-IS/N2090110015/listing.html)
 

Place of Performance

Address: Denver Service Center, National Park Service, Denver, Colorado

Zip Code: 80228
 

Record

SN02329542-W 20101120/101118233944-7e622e0e7188da283e702a716fda7faa (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 |