Loren Data's SAM Daily™

fbodaily.com
Home Today's SAM Search Archives Numbered Notes CBD Archives Subscribe
FBO DAILY ISSUE OF JULY 18, 2002 FBO #0228
SOURCES SOUGHT

70 -- USAMISSA Domino Support

Notice Date
7/16/2002
 
Notice Type
Sources Sought
 
Contracting Office
General Services Administration, Federal Technology Service (FTS), FTS, 7T-6 Southwest Texas, 727 E. Durango, Rm A105, San Antonio, TX, 78206-1283
 
ZIP Code
78206-1283
 
Solicitation Number
7TF-02-0008
 
Response Due
8/16/2002
 
Point of Contact
Joe Eason, Contracting Officer, Phone (210) 472-5050, Fax (210) 472-5054,
 
E-Mail Address
joe.eason@gsa.gov
 
Small Business Set-Aside
Total Small Business
 
Description
GSA INTENDS TO MALE A SOLE SOURCE AWARD TO Madcap Media, 18531 Fourmile Creek, San antonio, TX 78217 PROJECT# FE212615T6 U.S. Army Medical Information Systems and Services Agency Application Technology Division Domino Application Development Support Statement of Work A. DATE: 26 JUN 2002 B. SHORT TITLE: Domino Support C.1 Scope of Work. The U.S. Army Medical Command (MEDCOM) is responsible for obtaining and maintaining communications and functional information support systems throughout their respective commands. MEDCOM has deployed Domino to facilitate communications and increase staff productivity throughout the AMEDD. Domino is a groupware application that allows workgroups to share information across local-area-networks, wide-area-networks, and dial-up lines. Domino consists of two key components: The Domino server and the Domino workstation. The Domino server provides services to Lotus Notes workstations including storage and replication of shared databases and mail routing. MEDCOM has established a 20-server Domino Network worldwide. Reference Memorandum, MCIM, 3 May 01, subject: Action Plans for U.S. Army Medical Department (AMEDD) Information Management Priority Projects, the ACSIM tasked USAMISSA to provide a recommendation and plan for Domino migration to a Microsoft-compatible application that will operate on the enterprise mail system. USAMISSA recommended and provided a plan for limited migration and coexistence between Domino and Microsoft. The main solution for Microsoft will be Webstore, which is implemented in Sharepoint Portal Server and Exchange 2000. As Exchange 2000 is deployed, Public Folder replication will be used to extend the reach of the applications. Contractors engaged in the coexistence/migration must have an understanding of both Lotus Notes/Domino and Microsoft Exchange Server. It is critical that we approach the coexistence/migration with a deep technological comprehension of both products. C.1.2 Objectives. To establish coexistence and limited migration between Domino and Microsoft as well as obtain central support for Domino application development for the AMEDD. Activities include, but not limited to, registration, re-registration, deletion of servers and users, monitoring and adjustment of network resources, development and monitoring of replication schedules, development and monitoring of mail routing. C.1.3 Hours of Operation. Work will normally be performed during normal duty hours, Monday-Friday, excluding federal holidays, 8 hours per day during the period 0700 to 1630 with one hour for lunch. A tour of duty shall be established with the Technical Manager (TM) and the Contracting Officer Representative (COR) upon contract award. Total hours of performance shall not exceed the number of hours ordered in the schedule. Subject to prior approval, variation in work schedule is acceptable when the total contract hours are not exceeded and no obligation is incurred requiring contract personnel to be paid overtime. If required, overtime will be worked ONLY with approval from an authorized Government agent, such as the TM, COR, or Contracting Officer (KO). In the event of office closure due to inclement weather, the contractor shall report to work unless otherwise directed by their company supervisor and/or the COR/TM/KO. This is a non-severable task due to the continuous nature of these services. Management information requirements would be at risk if support were not maintained during the transition between program periods. C.1.3.1 Place of Performance. Work shall be performed on-site at USAMISSA, , 2455 NE Loop 410, Ste 150, San Antonio, TX 78217-5607. C.1.3.2 Level of Effort. The Government estimates approximate hours as follows: Senior Information Engineer (2 FTE). C.1.3.3 Travel. Contractor travel expenses will be equivalent to the JTR and a request will be submitted prior to performance of the travel to the COR for approval. After travel has occurred, a detailed invoice with a breakdown of expenses will be submitted to the COR. Contractor personnel may be required to perform temporary duty (TDY) to accomplish taskings. The contractor shall be responsible for airline scheduling and ticket costs. The approval authority for travel will be the government TM. C.1.3.4 Travel Security Briefing. Contractor personnel traveling for the purpose of performing temporary duty (TDY) outside the 50 United States, its territories and possessions, require an Antiterrorism (AT) and Force Protection (FP) briefing within 6 months of travel. The briefing includes viewing a Force Protection video, and receiving an additional briefing from a certified AT/FP instructor (including area specific information). The TM and USAMISSA Security Manger shall assist in scheduling these briefings. C.1.3.5 Guidance from Headquarters, U.S. Army, Europe, and Seventh Army, DOD Contractor Personnel Office, requires that ALL Contractor personnel complete a Request for Confirmation of Exemption from the Requirement to Obtain a Work Permit (via fax) through the European Regional Medical Command to the German BadenWurt Office in Stuttgart if Contractor personnel who will be entering the country of Germany for short-term TDY travel. (A short-term TDY consists of 90 days or less.) Any individual, as well as the corporation who employees the individual, who stays 91 days or longer is automatically subject to payment of German taxes and/or fine(s) upon departure from Germany. If approved, by the German Government, this exemption will allow tax-free status for the duration of the approved TDY period. Failure to comply with this requirement puts the individual, the corporation that employs the individual, as well as the Government, at risk for potential fines, German taxes, and/or other actions. Compliance is mandatory. The TM shall provide assistance for this requirement. C.3. Contractor Furnished Items. The contractor shall provide core staff members with the knowledge, skills and abilities to perform the listed duties in section C.5. C.4. Equipment. Contractor personnel shall be responsible for all equipment issued and shall maintain equipment in accordance with proper office procedures. Government equipment will be used only in performance of requirement of this contract. Equipment shall not leave the building without prior approval of the Technical Manager and issue of a hand receipt. Contractor personnel shall not modify or load unauthorized software to computer equipment without prior approval by the government. Contractor personnel will be provided access to required information to analyze functional and technical requirements of the MEDCOM System. Contractor will also have access to MEDCOM hardware and software necessary to support the MEDCOM. C.5 Specific Tasks. C.5.1 Information Engineers. The contractor shall provide assistance in administering the Lotus Notes servers throughout the MEDCOM-supported sites. The contractor will provide customer support to include assistance to Site Administrators. The contractor shall provide continuing Lotus Notes system administration support throughout the period of performance, which includes, but not limited to, the following services: (1) Registration/Re-registration of IDs. -a- Servers -b- Users -c- Certifiers (2) Cross Certification of IDs. -a- Servers -b- Users (3) Replication of servers. -a- Create replication schedules -b- Monitor execution/performance -c- Create replicas (4) Mail Administration. -a- Create routing schedules -b- Monitor execution/performance (5) Installation of software. -a- Servers -b- Users -c- Large databases (6) Server maintenance -a- Monitor disk usage -b- Monitor overall performance -c- Backup -d- Crash recovery (7) Investigate crashes and report/document findings. (8) Establish Mail connectivity between Lotus Notes and Microsoft. Allow regular mail messages to be sent back and forth between Exchange and Notes. For completeness, mail connectivity should include support not just for ordinary Message and Reply forms, but also for extended mail forms such as Telephone Messages, Tasks, and Routing Slips. (9) Set up Directory synchronization between Lotus Notes and Microsoft. Establish bidirectional synchronization of Exchange and Notes directories that allows access to complete and accurate address information to users on either system. (10) Replicate Lotus Notes discussion and document distribution databases using Exchange/Outlook public folders. (11) Perform Forms mapping for template or instant workgroup software applications. Provide mapping between the simple template application supplied by Lotus Notes and the instant workgroup software applications supplied by Microsoft Outlook. (12) Perform Directory entry migration. Create new Exchange directory entries, and possibly Microsoft Windows accounts for Notes users or match Notes directory entries to existing Windows and Exchange accounts. Either convert Exchange custom recipients who refer to migrating Notes users to native Exchange entries or delete them. (13) Perform Public Address Book (PAB) migration. Migrate Public Address Book to Exchange/Outlook Personal Address Books for VET Services users. (14) Perform Mailbox migration. Create Exchange mailboxes for VET Services users. Migrating mailbox also includes preserving the hierarchy and contents of private folders between Notes and Exchange. (15) Maintain a list of index workspace names, the SPS on which they are stored, and the server and workspace to which they are propagated. C.5.3 Project and Resource Management. Contractor personnel shall utilize the project and resource management tool, PlanView. The government shall furnish licenses and training. Contractor personnel may perform one or all of the following tasks: input the breakdown of work and tasks, add schedule information, assign resources, collect time, input time and close work. The government shall schedule and initial meetings with contractor personnel and contractor managers to discuss the role of contractor personnel, and the goals and objectives of this requirement. C.5.4 Deliverables. Deliverable Due Date Updated Name and Address Book end of each month Plan View Data Entry end of each week Server Performance Report end of each month Server Data Backups end of each day New Server and Client Ids/SW Installs NLT 10 days after request New Database Replicas NLT 1 day after request Updated Replication Schedule NLT 5 days after request Updated Mail Routing Schedule NLT 5 days after request C.6. Documents. The Contractor shall adhere to the policies and procedures as outlined in the documentation indicated below. C.6.1 Defense Information Infrastructure (DII) Common Operating Environment (COE) Integration And Runtime Specification (I&RTS), Version 2.0, 23 October 1995 C.6.2 Military Health Services System (MHSS) Functional Area Model - Data (FAM-D) C.6.3 Military Health Services System (MHSS) Functional Area Model - Activity (FAM-A) C.6.4 Defense Data Dictionary System (DDDS), latest version. C.6.5 MHS Automated Information System (AIS) Security Policy Manual, Version 1.0, April 1992. C.6.6 MIL-STD 973, ?Configuration Management,? 17 April 19912 C.6.7 NBS SP500-153, ?Guide to Auditing for Controls and Security: A System Development Life- Cycle Approach,? April 1988 C.6.8 DOD Manual 8020.1-M, Functional Process Improvement, 15 January 1993. C.6.9 DOD Regulation 5200.2-R, ?DOD Personnel Security Program,? January 1987. C.6.10 DOD Regulation 5000.2-R, ?Mandatory Procedures for Major Defense Acquisition Programs (MDAP) and Major Automated Information System Acquisition Programs (MAISAPs),? 6 October 1997. C.6.11 Principle Deputy Assistance Secretary for Health Affairs (PDASD-HA Memo, ?Use of DOD Standards in MHS Migration Systems,? 11 March 1996). C.6.12 Exemption 2 through 9 DoD Privacy Act Program: DoD 5400.7-R C.6.13 Acquisition Documentation Security Markings, dated 15 Feb 94. C.6.14 AR 380-19, Annex D, System Accreditation Requirements C.6.15 MEDCOM Domino Application Development Standards C.6.16 MEDCOM Domino System Administration Standards C.6.17 MIL-STD 498, dated 5 December 1994, Software Development & Documentation C.6.18 DISA, Technical Architecture Framework for Information Management (TAFIM) C.6.19 MHSS Health Area Standards Profile C.6.20 MHSS Standard Communications Architecture C.6.21 MHSS Standard Security Architecture C.8 Period of Performance: The initial period of performance: 1 October 2002 - 30 September 2003. The Government request 4 (four) option years as follows: Option 1 1 October 2003 to 30 September 2004 Option 2 1 October 2004 to 30 September 2005 Option 3 1 October 2005 to 30 September 2006 Option 4 1 October 2006 to 30 September 2007
 
Place of Performance
Address: 2455 NE Loop 410, Suite 150, San Antonio, TX
Zip Code: 782175607
Country: USA
 
Record
SN00117852-W 20020718/020717062209 (fbodaily.com)
 
Source
FedBizOpps.gov 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.