N6264511R0027N62645 11 R 0027FINALRELEASED by waX60pA

VIEWS: 6 PAGES: 93

									                                                                                         1. REQUISITION NUMBER
SOLICITATION/CONTRACT/ORDER FOR COMMERCIAL ITEMS                                                                                                      PAGE 1 OF        93
         OFFEROR TO COMPLETE BLOCKS 12, 17, 23, 24, AND 30
2. CONTRACT NO.                    3. AWARD/EFFECTIVE DATE   4. ORDER NUMBER                         5. SOLICITATION NUMBER                         6. SOLICITATION ISSUE DATE
                                                                                                     N62645-11-R-0027                               31-Aug-2011
7. FOR SOLICITATION                a. NAME                                                           b. TELEPHONE NUMBER      (No Collect Calls)    8. OFFER DUE DATE/LOCAL TIME
   INFORMATION CALL:               COURTNEY A. PIAR                                                                                                 09:00 AM 03 Oct 2011
                                                                                                     301-619-7467
9. ISSUED BY                        CODE                            10. THIS ACQUISITION IS                       11. DELIVERY FOR FOB              12. DISCOUNT TERMS
                                               N62645
                                                                    X UNRESTRICTED                                DESTINATION UNLESS
NAVAL MEDICAL LOGISTICS COMMAND
                                                                                                                  BLOCK IS MARKED
693 NEIMAN STREET                                                      SET ASIDE:                % FOR
FORT DETRICK MD 21702-9239                                                                                            SEE SCHEDULE
                                                                            SB
                                                                            HUBZONE SB                                13a. THIS CONTRACT IS A RATED ORDER
                                                                                                                      UNDER DPAS (15 CFR 700)
                                                                            8(A)
                                                                                                                  13b. RATING
                                                                            SVC-DISABLED VET-OWNED SB
TEL:                                                                                                              14. METHOD OF SOLICITATION
                                                                            EMERGING SB
FAX:                                                                                                                  RFQ                   IFB             X RFP
                                                                    SIZE STD:      500         NAICS:   423450
15. DELIVER TO                      CODE      N00000                16. ADMINISTERED BY                                                        CODE
SEE DELIVERY/TASK ORDERS
SEE DO/TO
SEE DO/TO MD
TEL:     FAX:




17a.CONTRACTOR/ OFFEROR                        CODE                 18a. PAY MENT WILL BE MADE BY                                                  CODE




                                             FACILITY
TEL.                                         CODE

     17b. CHECK IF REMITTANCE IS DIFFERENT AND PUT                  18b. SUBMIT INVOICES TO ADDRESS SHOWN IN BLOCK 18a. UNLESS BLOCK
     SUCH ADDRESS IN OFFER                                          BELOW IS CHECKED         SEE ADDENDUM
  19. ITEM NO.                    20. SCHEDULE OF SUPPLIES/ SERVICES                            21. QUANTITY          22. UNIT       23. UNIT PRICE         24. AMOUNT



                                               SEE SCHEDULE

 25. ACCOUNTING AND APPROPRIATION DATA                                                                                26. TOTAL AWARD AMOUNT (For Gov t. Use Only )




     27a. SOLICITATION INCORPORATES BY REFERENCE FAR 52.212-1. 52.212-4. FAR 52.212-3. 52.212-5 ARE ATTACHED.                    ADDENDA            ARE     ARE NOT ATTACHED
 0
     27b. CONTRACT/PURCHASE ORDER INCORPORATES BY REFERENCE FAR 52.212-4. FAR 52.212-5 IS ATTACHED.                              ADDENDA            ARE     ARE NOT ATTACHED

28. CONTRACTOR IS REQUIRED TO SIGN THIS DOCUMENT AND RETURN             1        COPIES        29. AWARD OF CONTRACT: REFERENCE
     TO ISSUING OFFICE. CONTRACTOR AGREES TO FURNISH AND DELIVER ALL ITEMS                         OFFER DATED               . Y OUR OFFER ON SOLICITATION
 X                                                                                                 (BLOCK 5), INCLUDING ANY ADDITIONS OR CHANGES WHICH ARE
     SET FORTH OR OTHERWISE IDENTIFIED ABOVE AND ON ANY ADDITIONAL SHEETS
     SUBJECT TO THE TERMS AND CONDITIONS SPECIFIED HEREIN.                                         SET FORTH HEREIN, IS ACCEPTED AS TO ITEMS:


30a. SIGNATURE OF OFFEROR/CONTRACTOR                                   31a.UNITED STATES OF AMERICA              (SIGNATURE OF CONTRACTING OFFICER) 31c. DATE SIGNED




30b. NAME AND TITLE OF SIGNER                    30c. DATE SIGNED      31b. NAME OF CONTRACTING OFFICER                  (TYPE OR PRINT)

(TYPE OR PRINT)


                                                                       TEL:                                            EMAIL:


AUTHORIZED FOR LOCAL REPRODUCTION                                                                                                 STANDARD FORM 1449 (REV 3/2005)
PREVIOUS EDITION IS NOT USABLE                                                                                                    Prescribed by GSA
                                                                                                                                  FAR (48 CFR) 53.212
   SOLICITATION/CONTRACT/ORDER FOR COMMERCIAL ITEMS                                                                                 PAGE 2 OF 93
                   (CONTINUED)
 19. ITEM NO.                      20. SCHEDULE OF SUPPLIES/ SERVICES                   21. QUANTITY    22. UNIT   23. UNIT PRICE      24. AMOUNT


                                          SEE SCHEDULE




32a. QUANTITY IN COLUMN 21 HAS BEEN
   RECEIVED       INSPECTED
                                 ACCEPTED, AND CONFORMS TO THE CONTRACT, EXCEPT AS NOTED: ______________________________________________________
32b. SIGNATURE OF AUTHORIZED GOVERNMENT                  32c. DATE           32d. PRINTED NAME AND TITLE OF AUTHORIZED GOVERNMENT
     REPRESENTATIVE                                                               REPRESENTATIVE




32e. MAILING ADDRESS OF AUTHORIZED GOVERNMENT REPRESENTATIVE                 32f . TELEPHONE NUMBER OF AUTHORIZED GOVERNMENT REPRESENTATIVE



                                                                             32g. E-MAIL OF AUTHORIZED GOVERNMENT REPRESENTATIVE




33. SHIP NUMBER           34. VOUCHER NUMBER          35. AMOUNT VERIFIED           36. PAY MENT                            37. CHECK NUMBER
                                                           CORRECT FOR
                                                                                            COMPLETE   PARTIAL     FINAL
    PARTIAL       FINAL
38. S/R ACCOUNT NUMBER       39. S/R VOUCHER NUMBER   40. PAID BY



41a. I CERTIFY THIS ACCOUNT IS CORRECT AND PROPER FOR PAY MENT 42a. RECEIVED BY (Print)
41b. SIGNATURE AND TITLE OF CERTIFY ING OFFICER    41c. DATE

                                                                     42b. RECEIVED AT (Location)


                                                                     42c. DATE REC'D (YY/MM/DD)    42d. TOTAL CONTAINERS



AUTHORIZED FOR LOCAL REPRODUCTION                                                                       STANDARD FORM 1449 (REV 3/2005) BACK
PREVIOUS EDITION IS NOT USABLE                                                                          Prescribed by GSA
                                                                                                        FAR (48 CFR) 53.212
                                                                            N62645-11-R-0027

                                                                                  Page 3 of 93

Section SF 1449 - CONTINUATION SHEET

SECTION A
The North American Industry Classification System (NAICS) code for this requirement is
423450. The Small Business Administration (SBA) size standard for this NAICS code is 500
employees. There are no set aside restrictions for this requirement. All qualified offerors
are invited to submit a proposal.


Proposal shall be returned NLT 03 October 2011 to the following address:
Naval Medical Logistics Command
Code 02
693 Neiman Street
Frederick, MD 21702
Attn: C. Piar N62645-11-R-0027

In addition, please provide details on all of the following:

Is Item on VA/GSA Contract Number: ___Yes or ___ No: If Yes please specify number:

If on Schedule provide Federal Supply Class Group, Part and SIN#:

Maximum Order Limitation on schedule per SIN#_____________

Is Product made in the USA?
If not, what country is it made in?

Complete company name and address:
Fax number:
Tax Identification Number (TIN):
Cage Code:
DUNS number:

Is your company a large, small, small woman owned, disadvantaged, or 8A business?

Is your company familiar with Wide Area Work Flow (WAWF) (electronic invoicing)?

Will your company accept an order with multiple ships to addresses?

What is your company’s preferred method of receiving an order (i.e.; Email, Fax, Mail)?

Contact 1
Company Name: _____________________________
Name and Title: _____________________________
Phone Number: _____________________________
                                                                               N62645-11-R-0027

                                                                                     Page 4 of 93

Email Address: _____________________________


Contact 2
Company Name: _____________________________
Name and Title: _____________________________
Phone Number: _____________________________
Email Address: ______________________________




SECTION B
B.1. The Contractor shall furnish Pharmacy Automation in accordance with the Generic
Functional Systems Requirement (GFSR) and site specific requirements as specified, on
individual Delivery Orders for these requirements, and all other terms and conditions set
forth herein.

B.2. This solicitation will result in multiple Indefinite-Delivery, Indefinite-Quantity (IDIQ)
contract awards, as identified under FAR 16.504(c). Delivery Orders will be awarded on a
firm fixed price basis.

B.3. The following activity is the sole authority to issue Delivery Orders: Naval Medical
Logistics Command, Code 02, 693 Neiman Street, Fort Detrick, MD 21702-9203.

B.4. The Contracting Officer will order Pharmacy Automation against the contract through
issuance of Delivery Orders via a DD Form 1155 or 1449 signed by the Contracting Officer.
Delivery Orders will be executed in writing by the Contracting Officer and transmitted
either via facsimile or electronically via e-mail. The contractor shall acknowledge receipt
via e-mail.

B.5. Each Delivery Order will contain at a minimum the following information:

a. The date of order
b. Contract number and order number
c. Description of the requirement
d. Pricing Information
e. The period of performance
f. Accounting and appropriations data
g. Payment office address
h. Invoicing and acceptance instructions
i. Any other pertinent data
                                                                                        N62645-11-R-0027

                                                                                             Page 5 of 93

       B.6. In the event that performance requirements at a particular facility differ slightly from
       that expressed in Section C, those differences shall be defined in the Delivery Order
       Proposal Request and resultant delivery order.

       B.7. The ordering period begins with the initial start of contract and is estimated to be 60
       months. The ordering period will end before 60 months if maximum quantities are
       reached.

       B.9. Instructions and procedures for Delivery Order preparation and award are contained
       in Section H of this solicitation.




ITEM NO      SUPPLIES/SERVICES              MAX           UNIT             UNIT PRICE           MAX AMOUNT
                                         QUANTITY
0001                                          8             Lot
            Pharmacy Automation - Large Site
            FFP
            Pricing shall be the complete pharmacy system as defined in the GFSR and
            supplemented by Attachment 6, Pricing Configuration for Large Sites.
            FOB: Destination




                                                                          MAX
                                                                       NET AMT
                                                                                      N62645-11-R-0027

                                                                                           Page 6 of 93

ITEM NO   SUPPLIES/SERVICES               MAX           UNIT             UNIT PRICE           MAX AMOUNT
                                       QUANTITY
0002                                        18            Lot
          Pharmacy Automation - Medium Site
          FFP
          Pricing shall be the complete pharmacy system as defined in the GFSR and
          supplemented by Attachment 6, Pricing Configuration for Medium Sites.
          FOB: Destination




                                                                        MAX
                                                                     NET AMT




ITEM NO   SUPPLIES/SERVICES           MAX             UNIT            UNIT PRICE              MAX AMOUNT
                                    QUANTITY
0003                                   130              Lot
          Support Services
          FFP
          FOB: Destination




                                                                        MAX
                                                                     NET AMT
                                                                                                    N62645-11-R-0027

                                                                                                         Page 7 of 93

ITEM NO       SUPPLIES/SERVICES              MAX               UNIT             UNIT PRICE                  MAX AMOUNT
                                           QUANTITY
0004                                          26                  Lot
              Installation
              FFP
              Installation for site specific delivery orders. Standard installation of equipment.
              FOB: Destination




                                                                                  MAX
                                                                               NET AMT




ITEM NO       SUPPLIES/SERVICES              MAX               UNIT             UNIT PRICE                  MAX AMOUNT
                                           QUANTITY
0005                                          26                  Lot
              Site Preparation
              FFP
              Site Preparation for individual delivery orders. Vendors shall perform site
              renovations related to the installation and use of the proposed solution such as
              electrical routing, patch work and cosmetic clean-up work after installation as
              defined in Section 8.1 of the GFSR.
              FOB: Destination




                                                                                  MAX
                                                                               NET AMT




       DELIVERY INFORMATION

       CLIN     DELIVERY DATE                 QUANTITY             SHIP TO ADDRESS                         UIC

       0001     POP 01-JAN-2012 TO            N/A                  SEE DELIVERY/TASK ORDERS                N00000
                31-DEC-2017                                        SEE DO/TO
                                                                   SEE DO/TO MD
                                                                   FOB: Destination
                                                                                   N62645-11-R-0027

                                                                                          Page 8 of 93

0002    POP 01-JAN-2012 TO        N/A             (SAME AS PREVIOUS LOCATION)              N00000
        31-DEC-2017                               FOB: Destination

0003    POP 01-JAN-2012 TO        N/A             (SAME AS PREVIOUS LOCATION)              N00000
        31-DEC-2017                               FOB: Destination

0004    POP 01-JAN-2012 TO        N/A             (SAME AS PREVIOUS LOCATION)              N00000
        31-DEC-2017                               FOB: Destination

0005    POP 01-JAN-2012 TO        N/A             (SAME AS PREVIOUS LOCATION)              N00000
        31-DEC-2017                               FOB: Destination


SECTION B



CONTRACT MINIMUM/MAXIMUM QUANTITY AND CONTRACT VALUE

The minimum quantity and contract value for all orders issued against this contract shall not be
less than the minimum quantity and contract value stated in the following table. The maximum
quantity and contract value for all orders issued against this contract shall not exceed the
maximum quantity and contract value stated in the following table.

MINIMUM              MINIMUM               MAXIMUM              MAXIMUM
QUANTITY             AMOUNT                QUANTITY             AMOUNT
                     $25,000.00                                 $49,000,000.00




SECTION C
Navy Pharmacy Generic Functional Systems Requirement (GFSR)
1.0 Overview
Some Navy outpatient pharmacies currently contain automated Accumed counters that are
approaching “end-of-life” and as of September 2012 will no longer be supported by the vendor. In
addition to the equipment that will no longer be supported, there are various different flow
approaches and equipment currently in use. This program is designed to replace the obsolete
equipment and provide a more standardized process flow for many of the naval outpatient
pharmacies.

Another major objective for the program is to improve the quality of dispensing. The pharmacies
currently vary from manual operations directed by “paper” to some limited automation controlled
by process flow software. It is the goal of this program to improve the overall quality by reducing
the opportunities for errors. It has been shown that extremely high levels of quality can be attained
by complete automation and system controlled manual dispensing.
                                                                                    N62645-11-R-0027

                                                                                           Page 9 of 93

A third objective of this program is to increase the volume capability of the various pharmacies.
Currently consumer satisfaction is primarily measured by customer wait time. It is the goal of this
program to increase the volume capability of the pharmacies within the currently allocated space
while reducing the wait time to be less than thirty minutes for at least ninety percent of the
customers during peak hours (thirty minutes including a ten minute maximum processing time).
Since the customer has a choice to wait or to utilize alternative commercial retail pharmacies
(through TRICARE), reducing the wait time per the goal stated, is anticipated and hoped to drive
increased volume.

Other objectives of this program is to reduce operating costs related to improved inventory
management (i.e. un-utilized, expired medications, medication quantity ordering), efficient staff
utilization while maintain protection of Personally Identifiable Information (PII) and increase
security.

Currently many of the outpatient pharmacies also process refills. At some pharmacies, the refills
are processed during the normal working day while at others, refills are accomplished off-shift.
The process flow software of a proposed system shall enable refills to be filled either during the
normal working day (but with a low priority so as to not impact customer wait time) or to be
deferred to off-shift processing.

There are currently several process models being utilized within Navy pharmacies. This section
will describe the process flow design that is to be implemented at the “medium” to “large”
pharmacies. A different process flow model may be utilized at the “small” Naval pharmacies. The
table below defines loosely what constitutes small, medium and large pharmacies. Small
pharmacies are included for information purposes only and are not included in this procurement.

         Pharmacy Size     Daily Initial     Fill   Rx   per    day Annual Initial Fill Rx
                           (weekdays)

         Large             1000 +                                     200,000+

         Medium            500-1000                                   100,000-200,000

         Small             500 and less                               100,000 and less

Other factors such as available pharmacy footprint and staff may affect classification of specific
pharmacies. For instance, a pharmacy that processes volumes normally classified as “medium”
may be reclassified as “small” due to size limitations that could limit its operational model options.
1. PROCESS REQUIREMENTS
This document shall refer to the Work Flow Management System (WFMS) as the software used by a
system to coordinate the actions of the centralized pharmacy management system.

Four functional components of a centralized pharmacy management system for large-size and
middle-size medical treatment facilities (MTFs) to meet the above objectives would include: a)
script receipt/order entry, b) automation of distribution process (i.e. dispensing, packaging,
labeling, pharmacy verification), c) operations controls (i.e. checks and balances, safety, reporting,
electronic documentation) and d) inventory/system management.
1.1. Order Entry
                                                                                    N62645-11-R-0027

                                                                                         Page 10 of 93

Script receipt and order entry shall consist of a customer queuing system and intake of
prescription information into the centralized automated system. The customer queuing system
shall be an interface to allow a customer to interface with the centralized automation system to
begin processing of prescription order(s). The queuing station/interface shall provide the
customer with ticket printed with a unique number and a bar code containing the same unique
number. The Queuing system shall include a monitor and annunciation systems to alert customers
when to approach and which window to go to.

The intake process shall be accomplished via interface to CHCS or manual entry. The system shall
provide access to all pertinent patient demographic information sent from CHCS or other host
system in real-time upon transmission to the automation system, requiring no manual entry. A
customer shall provide their unique ticket to the pharmacy technician to begin the process.
Prescription order information from CHCS shall be downloaded into the WFMS or shall be manual
entered. The automation shall provide barcode capability, both commercial and locally generated
formats. The unique number identifier created in CHCS or host system shall relate directly to the
unique bar code generated by the system for prescription processing. The system shall provide a
method to display the origin of the order entry and where a prescription is in the workflow,
including status. The system shall be capable of using and displaying multiple unique patient
identifiers based on DoD practice standards as well as industry standard patient identifiers.
1.2. Automation of Distribution Process
Once an order is received, orders shall be prioritized. The WFMS shall provide a flexible scheduling
algorithm taking into account multiple factors including but not limited to: a) amount of time the
order has been waiting in queue, b) type of customer (i.e. just discharged in uniform), and c)
capability of the system fulfill the order, refill. The WFMS shall allow for configuration priority
settings of each factor as well as configurable queued order maximums per station in process flow.
The scheduling algorithm shall be capable of taking into account number of orders currently in
queuing for a specific location in the process flow, avoiding gridlock based on queued orders at a
particular location, ability of automated dispensing and any manual dispensing stations to continue
fulfillment of orders if a gridlock occurs or if station has reached its configured queue maximum
setting.

The WFMS shall support a prioritization function that shall allow pharmacy staff to make running
changes as required. This shall permit the pharmacy staff to have a degree of control to react to
situations and demand fluctuations that may occur throughout the day. The WFMS shall be capable
of interweaving Rx refills based on capacity available (lowest priority) or holding the refill Rx’s to
process off-shift. The system shall provide the capability to collate/group prescriptions by patient
or family. The system shall provide a method to prevent vials from spilling drugs dispensed into
them as the vials move through the process until provided to customer.
       1.2.1. Automatic Print and Fold
                                                                                    N62645-11-R-0027

                                                                                         Page 11 of 93

The WFMS system shall be capable of automatically printing drug information sheets for each
prescription in the order. The vendor shall provide a methodology for providing any special
information sheets or guides for patients such as the FDA Risk Evaluation and Mitigation Strategy
(REMS). The WFMS shall select the required sheets for each order from a database of drug
information sheets. A means to keep such a database current shall be provided. A print packet file
with all required drug information sheets required for a single order shall be sent to the printer
and, if there is more than one sheet in the order, staple the packet and be Z-folded. The complete,
Z-folded drug information package shall be bar code scanned before medications in a particular
order begin to be filled and shall be kept with its relevant order throughout the entire distribution
process and the order is present to the customer. Refill orders need not be provided drug
information sheets.
           1.2.1.1.    Printer Requirements
Black and white laser printers shall be provided. The printer shall be capable of a minimum of 600
dpi. Printers shall be capable of utilizing 20 pound, 8-1/2” by 11” paper. The printer shall be
capable of pulling blank sheets from multiple paper cassettes so that one can be refilled while
another is in use without interrupting production.

An alternate path shall be provided for the printed pages to enable the printer to reject pages that
were in process during a “jam” and may not have been properly printed or fused. The printer shall
automatically recover from jammed situations without creating any potential for wrong sheets to
get into an order packet.

The printer shall be capable of producing the first printed sheet within 10 seconds after the file is
send to the printer. The 10 seconds shall include spooling the printer up from idle and processing
the first page. If the printer is spooled up, the printer shall be capable of printing a minimum of 30
pages per minute.

An indicator shall be provided that would inform the operator when a paper cassette is empty.
           1.2.1.2.    Z-Folder Requirements
The Z-Folder shall be capable of a folding rate that can keep up with the printer. Only packets
containing drug information sheets for all medications associated with an order are to be fed from
the printer into the Z-Folder. The Z-Fold orientation shall be so that view of the order’s bar code is
not obstructed.

If an order exceeds the maximum page capacity of the Z-folder, the WFMS shall break the print file
into multiple batches and produce multiple Z-folded packets. Each packet shall have a unique bar
code so that each packet can be accounted for as they are released into the tote.
           1.2.1.3.    Backup Printer
A backup printer shall be provided. This printer shall have the capability to staple order pages
together. The pages of an order that have been stapled together shall be manually folded. A
method to switch to the backup printer when the primary is down shall be provided. That method
shall also be capable of switching back to the primary printer when it is back on-line.

The backup printer shall have the same capacity, speed and performance as the primary printer.
       1.2.2. Automatic Tablet Dispensing Counters
                                                                                      N62645-11-R-0027

                                                                                           Page 12 of 93

Automated tablet counters shall be provided as part of the overall system. The Automatic Counter
Equipment shall interface to the WFMS and be directed by the WFMS. Automatic tablet dispensing
counters shall be responsible to count the correct tablets required by the Rx, select the correct vial
size, place the counted tablets into the vial, print and apply the correct patient label to the vial and
place the vial with the correct Z-folded drug information sheets. If a count cannot be completed
due to a problem (out of inventory, mechanical failure of specific counter), the system shall allow
the automatic counter to continue working, if applicable. The WFMS shall have a process to
prevent “problem” vials from being dispensing to the customer order. A method to enable partial
fills when no more inventory of that drug is available shall be provided. If a drug is available via
another location, the WFMS shall divert the order to the station containing the required drug. If the
entire automatic counting station goes down, the WFMS shall allow Rx fulfillment to continue using
the resources available. If an automated counter is down for an extended period, all Rx’s shall be
fulfilled using available resources. The system shall allow for a forcing function to ensure proper
filling of medication cells such that ability to access and utilize remaining cells shall be hindered.

A site specific Functional Requirements Document shall contain the specific requirements for the
automatic tablet counters to be implemented at a particular site, such as the overall throughput
rate and the number of drugs to dispense. This document shall discuss the general requirements
that are to be common across the various pharmacies contained in this contract.
           1.2.2.1.    Counting Cell Refill Process
The system shall allow the refill of medication dispensing cells without the need to bring down the
entire automated tablet dispensing system. The WFMS shall be capable of tracking the inventory in
each tablet counting cell within the Automated Counter Machine (ACM). The system shall provide
a means alert staff that refill a particular counting cell is required. The system shall allow for ACM
cell refill during normal operating hours as well as the end of the work day. The system shall
provide a means to ensure that the correct medication is filled into the correct dispensing cell,
preventing incorrect medication loading. The system shall be capable of tracking who refilled the
dispensing cell as well as maintain proper tracking of inventory, based on the removal of a refill
container from inventory for reporting purposes. The WFMS shall only schedule continued
medication counts from the refilled cell if there were no noted errors during the refill process.
           1.2.2.2.    Dispensing Cell Requirements
Each counting cell shall be capable of being set up by pharmacy staff for any drug that has been
authorized by the manufacturer for counting in the ACM. A list of all countable drugs shall be
provided as part of the system on a database that is frequently updated, without pharmacy staff
involvement, by the manufacturer. The database shall also contain the counting cell settings for
each drug.

When a counting cell is set up following the manufacturer’s guidelines for an NDC (National Drug
Code), the cell shall count tablets with an accuracy of ±1 tablet in 1,000 tablets (99.9%). When a
counting cell is set up for a new drug (first dispenses with this drug from this counting cell), the
WFMS shall be capable of setting a Quality Assurance (QA) flag for this vial which shall be cleared
prior to issuing an order to a patient. The vendor shall provide recommended QA procedures for
count accuracy.
           1.2.2.3.    Vial Size/Replenishment
                                                                                         N62645-11-R-0027

                                                                                               Page 13 of 93

The Automated Counter Machine (ACM) shall be capable of dispensing at least two different size
vials. The WFMS shall select the appropriate size vial based on the tablet size and quantity of
tablets. If the Rx shall not fit within a single vial, the WFMS shall be capable of requesting two or
more vials as required for the Rx. The bar code applied to each vial, assuming more than one vial is
required, shall be unique to identify each vial as a separate part of the Rx.

The ACM shall be capable of continuous operation without having to halt the automated dispensing
process to refill vial containers. If cassettes are utilized, there shall be at least two for each vial size
provided to allow refilling one cassette while the other is in use. Vendor shall provide a
recommendation for the vial sizes based on dispensing history at each pharmacy.
            1.2.2.4.    Labeling Requirement
The specific label size (length and height) shall be based on the height and circumference of the
smallest recommended vial size without overlap, folding or cutting by the person applying the
label. System shall be capable of assigning and printing accessory labels (i.e. Take with Food) as
determined by peer-reviewed, validated commercial product reference database. The contractor
shall provide the part number for the paper stock and ribbon stock required. Vendor shall indicate
if label and ribbon stock are available on vendor’s federal supply schedule and list all DoD
pharmacy prime vendors such label and ribbon stock are available through. The contractor shall
provide at least two cases of paper and ribbon stock of the selected part numbers to enable the
pharmacy time to obtain their own supply. The contractor shall provide all testing paper and
ribbon supplies that are not inclusive of the two cases.

The system shall print patient specific labels. All patient labels shall to be printed from the WFMS.
Patient labels shall be capable of including a description of the dispensed medication. All
information required to be printed for the patient, except the auxiliary drug warnings and drug
description (tablet shape, color, etc), shall be contained in the file received from CHCS. A local
database of the auxiliary drug warnings and drug descriptions shall be provided to and available
for utilization by the WFMS. A means of remotely updating this database on a regular basis by the
vendor without pharmacy staff involvement shall be included over the time period for maintenance
of the system.

A minimum 300 dpi printer shall be used to print all patient labels and applies to all label printers
both for the ACM (Automated Counter Machine) and manual stations.
            1.2.2.5.    Capping Requirement
If the Automatic Tablet Dispensing Counter is capable of applying the vial cap, a bulk cap loader
shall be utilized to replenish cap supply. Loading caps shall not require the operator to orient the
caps during the loading process. A low cap sensor shall be utilized to turn on/off the refill
indicator. The system may utilize a cassette in lieu of a hopper if the cassette can be
changed/replaced without stopping the machine. The system shall provide the capability of
applying child proof caps as the default cap.

These supplies shall be readily available on the vendor’s federal supply schedule. Sufficient caps
shall be provided as part of the system to enable the pharmacy to order and receive the caps after
installation and testing is complete.
            1.2.2.6.    Number of Dispensing Cells
                                                                                    N62645-11-R-0027

                                                                                         Page 14 of 93

The required number of drugs to be automated shall be specified in the site specific requirements
document. The general requirements are:

The minimum specific drug inventory contained within all ACM’s shall be sufficient to operate at
least 24 hours without requiring a cell refill.

The maximum specific drug inventory (maximum target tablet inventory in a cell) shall be
sufficient for no more than one week’s use (included to provide an upper bound for the slower
moving automated drugs).

A Pareto of the countable tablets shall be provided in the site specific document. Included with the
pareto shall be the NDC, drug name, Rx’s dispensed and the total tablet count over a specified
period of time.

If the counting methodology of the ACM utilizes NDC specific counters, spare counters shall be
provided to operate the ACM when manufacturer changes occur frequently (set one counter for
each manufacturer but only have one in the ACM). A total of five per cent spare counters shall be
provided as part of the ACM’s.
           1.2.2.7.    Minimum Throughput Rate
The throughput requirements shall vary across the pharmacies and shall be specified in site
specific document. The system shall be capable of achieving site specific minimum throughput on a
sustained basis (at least for 4 consecutive hours). Vendor shall provide for all proposed automatic
tablet dispensing counters.
           1.2.2.8.    Controlled Drug Requirement
ACM’s shall be capable of dispensing C3-5 control drugs in the ACM’s. A secondary locking method
shall be provided for up to 10% of the counting cells. The secondary locking method shall be used
for each counting cell individually or a “bank” of counting cells. Every cell shall require a primary
lock controlled by the ACM controller that is utilized as part of the cell refill process.

The cells designated for C3-5 drugs shall have the capability of having a different role based
security level for refill and maintenance than the other counters (configurable parameter).
Controlled drugs shall be refilled using the same process as the other counts as indicated, with the
exception of the additional secondary locking method. A separate report shall be available listing
individuals, dates, times, and refill parameters for these cells.
           1.2.2.9.    Recovery Process Requirement
It is anticipated that faults and failures shall occur over time. The system being provided shall
include a simple means of recovering from these faults or failures. When possible, automatic
recovery from a fault or failure shall be provided. If a fault or failure occurs, a Quality Assurance
(QA) request shall be generated for any vial being filled during the fault or failure on the unit.
       1.2.3. Manual Stations
                                                                                      N62645-11-R-0027

                                                                                           Page 15 of 93

As automatic tablet dispensing counters shall not be capable of dispensing all required
prescriptions required by a pharmacy due to inventory or form of the prescription (i.e. liquid vials,
inhalers, creams), manual fill stations shall be required to handle such non-oral solid medications.
Manual filling stations shall have storage to house non-automated, non-refrigerated, non-C2 items
and non-auxiliary drugs. The design of the manual station shall prevent station operators from
working on more than one customer order at a time to prevent prescription errors. If required by
the site, Refrigerated and C2 dispensing stations shall be provided. Manual Stations shall either
have a fixed countertop height of 39 inches or shall have an adjustable countertop height which is
capable of 39 inches and +/- 2 inches in either direction.

The computer associated with the station shall be mounted in a position so as to not detract from
the station’s shelving. The work station shall have angled shelving above the work desk in which
the heights between the shelving can be manipulated to accommodate items of variable heights.
The shelves shall also pull out to allow ease for refilling line items from the back to ensure first-in,
first-out inventory management principles. Drawers which shall allow for the heights of the
drawers to be manipulated to accommodate items of variable heights shall be located under the
work desk. The drawers shall also pull out for easy accessibility and ease of refilling items from the
back to ensure first-in, first-out inventory management principles maintained.

Bulk shelving, in addition to workstation shelving, shall be provided to house slower moving drugs.
Bulk shelving shall also have heights between the shelving that can be manipulated to
accommodate items of variable heights. The bulk shelving shall also pull out to allow ease for
refilling line items from the back to ensure first-in, first-out inventory management principles.

Shelving shall be provided to store medications such that medications shall be located at the
manual station based on how frequently they are used. Fast moving drugs shall be placed in close
proximity to the station operator. Slower moving drugs shall be stored further away from the
station operator. Very slow moving drugs shall be stored in bulk shelving outside, but near the
manual stations. Depending on the size and workload of individual pharmacies, may require
multiple manual stations or fast moving drug specific manual stations.

The dispensing equipment to be included with all manual stations shall include a client PC and
monitor with attached bar code scanner, a tablet counting assist and a patient label printer. The
requirements for the patient label printer are the same as specified in section 2.2.2.4.
           1.2.3.1.    Client PC and Monitor
A client PC shall be provided for all manual stations. The PC and software shall meet the security
requirements as specified in Section 3 and the Information Assurance Requirements Document.

The monitor shall be a flat panel monitor and be at least 20” diagonally.

The monitor shall be fully color capable and shall provide a resolution of at least 1280 X 720

No data shall be stored on this PC that is not recoverable from the server. A failure of a PC shall not
result in the loss of any data and shall be fully recoverable by replacing the PC.
           1.2.3.2.    Bar Code Scanner
                                                                                     N62645-11-R-0027

                                                                                          Page 16 of 93

The bar code scanner shall be capable of reading all “modern” 1-D and 2-D bar codes. The scanner
shall have a mount that permits “no-hands” usage. The scanner shall be able to be removed from
the mount for scanning bar codes in difficult to read locations.
           1.2.3.3.    Tablet Counting Assist
A tablet counting assist shall be provided to improve the count accuracy and speed of tablet
counting. The tablet counting assist shall be attached to the PC so that when the NDC scan occurs,
the counting assist is set for the desired tablet count without operator intervention.

If a weigh counting assist identified, a means shall be made available to update the weight per
tablet stored for any given drug. This weight per tablet table shall be updated by the contractor
without pharmacy staff intervention.
       1.2.4. Pharmacist Verification Station
The function of the Pharmacy Verification (PV) station shall be to permit a pharmacist to view the
entire order and verify that all items are both present and correct. The dispensing process shall
terminate at the PV station. At the PV station, a pharmacist shall be capable of scanning each
prescription to ensure the order includes all of the medications required. The reviewing
pharmacist shall be recorded for each dispense in the order and shall become the pharmacist of
record for this Rx. It shall be possible for more than one pharmacist to verify items in an order. In
addition to the counter required for the PV function, each PV position along the counter shall have
a PC, monitor and bar code scanner. PV Stations shall either have a fixed countertop height of 39
inches or shall have an adjustable countertop height which is capable of 39 inches and +/- 2 inches
in either direction.

The pharmacist shall be capable of viewing all relevant information to verify the ordering including
but not limited to a photocopy of paper scripts and a picture of the medication to assist in rapid
verification. Referenced images displayed shall be regularly updated remotely by the vendor and
shall not require pharmacy staff intervention. A process to handle missing items and medications
requiring refrigeration shall be provided. If an order is verified as complete, the WFMS shall
trigger the queuing system in the waiting area to call the correct customer (visually and audibly) to
an issue window to receive the order.

If the Pharmacist identifies an issue with an order, the WFMS shall provide a list of potential
problems to be selected by the Pharmacist to indicate the issue and the problem order shall be set
aside for correction. Once corrected, the order shall return to the PV station for review unless the
issue was corrected by a Pharmacist. If the issue was corrected by a Pharmacist, completion of
resolving the issue shall complete the order and call the customer to the issue window.
       1.2.5. Issue Window
The issue window operator shall scan the order into CHCS to be classified as issued. Scanning of
the order shall include each item in the order as well as the Z-folded drug information sheet, if not a
refill. There are two requirements for this functionality depending on the type of order.
                                                                                     N62645-11-R-0027

                                                                                          Page 17 of 93

       1. First Fills – The customer shall be called to the issue window upon successful
          completion of the PV process. When the customer reaches the window, the technician
          shall be able to correlate the customer to order. Each item in the order shall be scanned
          as they are presented to the customer or placed into a package for the customer. The
          technician shall scan each item in the order, including the drug information sheet
          packet(s) using the bar code on the first page of the packet. Completion of the scan of
          the last item in the order shall be used to indicate to WFMS that the order has been
          issued to the patient.

       2. Refills – These orders may be processed simultaneously with orders that customers are
          waiting for or may be processed during an off-shift period. Refills can be issued from
          the Issue Widow or from a dedicated pick-up window. In either case, the order shall be
          packaged and closed with a package tag applied. When packaging refill orders, the
          technician shall scan each item in the order as they are packaged. The scan of the
          correct package shall be used by WFMS to indicate that the order has been issued to the
          customer.

           Issue windows shall require a client PC with monitor, bar code scanner and a package
           tag printer. The equipment requirements are the same as previously defined for this
           equipment.
1.3. Operation Controls
All dispensing shall be directed and controlled by the WFMS. The system shall be designed to
prevent medication dispensing errors and cross-contamination of products during dispensing. The
system shall be capable of sorting orders by patient name, sponsor’s SSN, by priority, drug, date or
inventory location. The system shall utilize a method of scanning as a means of medication and
patient verification throughout the dispensing process including the automatic dispensing
counters, manual filling stations, PV stations and the issuing windows. The system shall confirm
that the medication is the correct formula and dosage as on the order. Also, the system shall be
capable of utilizing a method to identify if an order has been fulfilled in its entirety. The next drug
in an order shall be not dispensed until scan of the previous drug is completed, nor shall a label be
released until verified. The system shall also utilize a method to verify an order is correct,
complete ready to be issued to the patient or ready to be transferred to the next location in the
dispensing process to complete the order. The system shall have a means to minimize medication
errors due to sound-alike, look-alike medications.

The WFMS shall be capable of tracking and displaying the status of all orders in process from any
pharmacy workstations/terminals as well as from remote locations. The WFMS shall be capable of
routing an order through the system provided, including back-flowing the item to an upstream
station, if required. The system shall be capable of alerting pharmacy personnel when an order has
exceeded a configurable time period to ensure that any order that may have been set aside for any
reason does not get ignored or overlooked while a customer waits.
       1.3.1. Workload Balance Resources
                                                                                    N62645-11-R-0027

                                                                                         Page 18 of 93

The WFMS shall be capable of load balancing all dispensing functions. If a specific station is down
or its queue is full, the WFMS shall have the capability to recognize this and continue to utilize the
remaining stations. The WFMS shall have the capability to avoid grid locking the system due to a
failure of an automatic counting machine or a manual workstations being off-line or slow to
provide sustained throughput of the system. The system shall provide the capability to select a
patient to work on as well as switch between patients.
       1.3.2. Role Based Security
The WFMS shall have the capability to identify users and limit tasks that can be performed by an
individual based on the individual’s login and their “rights” (role based security). A local system
administrator shall be capable of changing an individual’s rights. At least five different levels of
rights shall be provided.
1.4. Inventory/System Management
As part of the centralized pharmacy management system, means of inventory management shall be
provided. The WFMS shall be capable of managing and tracking the inventory within the
pharmacy. The following features shall be provided as part of the Inventory Management:

      Maintain inventory in all dispense locations, forward stock areas (including manual filling
       stations, and bulk storage locations.

      Be capable of aggregating the total inventory contained within the pharmacy (all three
       storage types discussed above).

      Be capable of directing the movement of drugs from one storage type to another and the
       tracking this move (person moving the drug and the physical location of the drug).

      Be capable of printing a drug usage report (drugs and total quantities dispensed) on a daily,
       weekly and monthly basis.

      Store target inventory levels and configurable re-order levels for each drug in each storage
       location.

      Be capable of printing a list of all drugs falling below the re-order point and the quantity
       necessary to bring the level up to a configurable target quantity.

      Support the put-away functions by enabling the put-away individual to log into the system.
       A report capability shall be provided to generate a list of all inventories adjustments made
       (daily, weeks, etc). Another report shall be available that compares the suggested drug
       order to the received drug order.

      At some Navy pharmacies, some of the in-patient drugs are selected from the outpatient
       drug inventory. The system shall provide a means to track such usage of outpatient
       inventory for in-patient needs.

      A means of accounting for the inventory required for the compounding area shall be
       provided. The contractor shall propose a means for this inventory to be included as part of
       the overall pharmacy inventory that the WFMS is responsible to manage.
       1.4.1. Drug Expiration
                                                                                    N62645-11-R-0027

                                                                                         Page 19 of 93

The system shall be capable of tracking lot code and expiration date of medications. WFMS shall be
capable of setting a minimum time left on the expiry date. The WFMS shall be capable of verifying
the expiry date is within the allowable range for both medications to be dispensed by the automatic
counters and manual fill stations.

The WFMS shall be capable of printing out a daily and/or weekly report of the drugs and their
location within a configurable time period of expiring.
       1.4.2. Maintain Complete Dispense History
The WFMS shall keep a record for each order and for each item dispensed in the order. The record
shall include the workstation where each drug is dispensed, the individual who dispensed this
drug, the PV individual who checked the dispensed drug and date/time stamps for each individual
action on this order. The data shall be searchable by various parameters such as workstation,
individual, order, time period, etc. The system shall provide and maintain documentation including
reference images, any scanned images and prescription data sent from pharmacy host system.
Prescription information, including scanned image files, shall be maintained and accessible for at
least three years.
       1.4.3. Reporting
A suite of reports shall be provided that shall support managing the pharmacy. The system shall be
capable of importing/exporting delimited files. Extraction of data shall be supported using a data
at rest modality as well as other means. Specific requirements and formats shall to be developed
during the course of the first installation and approved by the Project Manager or their
representatives. It is anticipated that all reports shall be available at each location so that a
commonality of managing the pharmacy will evolve. If, during the course of the 2nd or 3rd pharmacy
installation additional reports are developed, these reports shall be made available to all
pharmacies.

Specific areas that are anticipated to require reports involve:

Quality – This category of report shall provide data on the number of wrong scans, by station or
function that has occurred during a configurable time period. Another report shall be available
based on the PV function – how many errors were caught or corrected by this process.

Service – A series of reports are anticipated that would report on customer wait times by time of
day. This wait time shall be broken down into its component parts (waiting in queue, processing
time, etc) to enable directing resources to the appropriate function. Statistical parameters shall be
computed for these times (i.e. time to complete 90 % of the customers, average wait times, peak
wait time, minimum wait time, etc).

Productivity - A series of reports shall focus on productivity parameters. These may include tasks
performed by individuals and/or station and include idle, average, mean, standard deviation and
peak process times, minimum throughput, transaction times by each phase of filling, utilization and
activity in the system. Another report shall provide statistical information of the work performed
by the automatic counters during a configurable time period.
                                                                                    N62645-11-R-0027

                                                                                         Page 20 of 93

Inventory - A series of reports should be developed that would report on the inventory status in the
pharmacy. A list of all drugs (including generic equivalents), their current inventory, target
inventory, trigger point and location code(s) shall be available. This list shall be sortable by area
and function within the pharmacy (i.e. ACM drugs, Fast Movers, Slow Movers, Bulk Storage,
Inpatient Drugs, etc). Another report shall identify expiring medications (lot numbers and
expiration dates). Another report shall be available to quantify drug ordering frequency and
quantity over a configurable time period. Another report shall compare the requested drug order
(order placed on day X) versus the received drug (received drugs on day X+1, X+2, etc). Another
report shall provide documentation of all manual stock bottle associations and mis-stocked
inventory locations with an audit trail. Another report shall list the inventory adjustments that
have been made (by time period) based on the counts that occur during the stocking function (this
provides a measure of inventory shrinkage).

Manual Station Re-stock Report: At the end of the dispensing day, a report shall be capable of being
produced for each manual station to facilitate the re-stocking process including:

      Storage location of medication to be restocked

      Name of medication to be restocked

      Quantity in units of item required for restock

Plannigramming – A report shall be available that would compute the drugs to be added or
removed from each of the dispensing station types (Automatic counting cells, manual stations). A
configurable time period shall be available so that the plannigram would be based on the previous
XX days of dispensing. A list of drugs to add or remove from each dispensing type shall be
calculated. A more complex report shall be available that would compute the drugs and their
preferred storage location by type of dispense station. This approach shall permit adding or
deleting drugs from the dispensing areas based on a configurable time period of previous usage by
using extra locations within each dispensing area.

Drug Location List – The system shall provide a report that is alphabetized by generic drug name
for all drugs in the pharmacy by station. This report shall indicate the current inventory and
location for this drug. This report shall be available for use by pharmacy technicians and
Pharmacist’s working in the inpatient pharmacy and as a backup for all the manual stations.

C2-5 Report – A report shall be available indicating the NDC, Pharmacist (or technician), dispensing
cell machine and number and date/time for all refills.

The transmission of reports shall include distribution to a designated central repository as well as
data at rest methodology. The report tools shall allow for a third party SQL reporting tool to access
the data to create customizable reports. The vendor shall supply a complete data dictionary. Data
shall, at a minimum, be available for reporting for three years.
2. SECURITY REQUIREMENTS
The following table provides a list of requirements for the ACM in combination with the WFMS.
The Priority/Type meaning is as follows: KPP-Key Performance Parameter which are rigid
requirements and C –Characteristics which are characteristics that are desired but not mandatory.
                                                                         N62645-11-R-0027

                                                                             Page 21 of 93



         Subgroup                         Requirement                     Priority/Type
                          1.1 The automation shall provide role
                          based security and process validation for            KPP
                          items loaded in the re-stocking process.
                          1.2 The vendor shall meet and maintain
                          Service specific security requirements to            KPP
                          include data at rest policies.
                          1.3 The vendor shall meet and maintain
                                                                               KPP
                          DIACAP or other required DoD Certification
                          1.4 The vendor shall meet and maintain
                                                                               KPP
                          HIPAA requirements
                          1.5 The automation shall provide roles
                          based access control configurable by site.
                                                                               KPP
                          The user defined roles shall, at a minimum,
                          control:
                          1.5.1 Approval authority for automation
                                                                                 C
                          reload
        1.0 Security
                          1.5.2 Prescription check authority based
                          on prescription origination (i.e. provider             C
                          entered; pharmacy entered, refill)
                          1.5.3 Authority to map a medication to a
                          dispensing automation including CHCS NDC               C
                          matching if necessary
                          1.6 The system shall securely maintain all
                          information related to prescription
                                                                               KPP
                          processing as dictated by DoD and local
                          policies.
                          1.7 The automation should provide a
                          method to lock or control entry into
                          designated medication cells (i.e. controlled
                                                                                 C
                          substances) or rows of cells to limit user
                          access to medications stored in a cell or
                          row of cells.
                          1.7.1 The automation should provide a
                          method to track and trace all access to any
                          locked cell and produce an alert or
                          indicator when access has been gained
                                                                                 C
                          without validated user authentication. The
                          system should provide an audit trail report
                          that a user can generate on all refilling
                          activities or cabinet access.
                          1.7.2 The automation should have at a
                          minimum two physical locks or methods of
                                                                                 C
                          restricting unauthorized access to the cells
                          or row of cells inside an automated robot.

3. QUALITY REQUIREMENTS
                                                                                    N62645-11-R-0027

                                                                                         Page 22 of 93

Quality is of paramount importance for the system being provided. The design and configuration of
the system proposed shall significantly reduce or eliminate opportunities for errors to occur.

The following quality features are required:

      1. Operators shall log into a workstation so that their tasks shall be limited to only the tasks
         they are authorized to perform. This is a feature to be included as part of the WFMS.

      2. Station operators shall never have multiple orders in process at once. When totes are
         manually moved, this opportunity exists.

      3. Stations shall never have multiple totes on their work counter at once. More than one
         tote provides the opportunity to place an item into the wrong tote.

      4. An item cannot be dispensed (patient label printed) without first scanning the NDC of the
         item to be labeled. Pre-printing of any labels creates opportunity to place a label on the
         wrong item.

      5. Location codes are to be used to direct a technician to the correct location for an item.
         This approach permits avoiding look-alike, sound-alike issues. Items that appear similar
         can be placed in different locations.

      6. Inventory is scanned to a location. Movement of this inventory to another location
         requires a scan of the next location and a scan of the individual’s ID that moved the item.

      7. Paper handling has been automated to avoid manual collation issues and insure the drug
         information sheets are inserted into a tote as part of the order.

      8. Automated dispensing process shall terminate at the PV station preventing the
         opportunity to bypass PV.

      9. ACM drugs are processed in a fully automatic mode.

      10. ACM cells are locked so that only a scan of the refilling technician’s ID and the refill
          container’s NDC shall unlock the cell. If a cassette counting cell hopper system is
          proposed, a similar process is required for refilling the cassettes and insuring the correct
          cassette is inserted into a counting cell.

      11. Manual filling stations are isolated from pass-by traffic to avoid distractions. This allows
          the technician to focus on the tasks at hand without interruption.
4. BUMED REQUIREMENTS
The following provides specific requirements promulgated by the Bureau of Medicine:
4.1. Information Assurance
Vendor shall meet all Navy Information Assurance (IA) requirements for Information Assurance
(IA) as specified by the attached IA requirements document.
4.2. Unique Identification
Vendor shall meet all requirements for Unique Identification (UID) per the most recent version of
Military Standard 130L (MIL-STD-130L) “Identification Marking of U.S. Military Property” and per
DFARS 252.211-7003 Item Identification and Valuation.
                                                                                    N62645-11-R-0027

                                                                                         Page 23 of 93

4.3. Project Management Plan
The vendor shall provide a project management plan (PMP) for each deployment of a proposed
solution. Their PMP shall provide a full description of services, roles and responsibilities, a work
breakdown structure, description of project phases, schedule, project reporting and tracking,
project activities and deliverables, quality plan, communication plan and risk management plan
with defined contingencies, project metrics and reports. There shall be an overall PMP tying
together all of the deployments with specified target dates for completion of each deployment and
overall end target of 30 September 2012.
4.4. Lifecycle Plan
The vendor shall provide a complete 5 year lifecycle plan describing the policies, procedures, and
practices governing the initiation, definition, design, development, deployment, operation,
maintenance, enhancement, and retirement of automated information systems (AIS), software,
equipment, hardware and other devices in their response. The plan shall provide all costs
associated for the 5 year lifecycle to include vendor maintenance and support in the same period.
4.5. Layout and Design
The vendor shall provide complete renderings for all suggested equipment depicted in layouts
specifics to each pharmacy as it exists today or shall exists at the time of deployment reflected in
the PMP.
4.6. Workflow for Solutions
The vendor shall supply a summary or explanation for all of the depicted layouts and their
respective workflows to include a rationale for any recommended solution. For example, if a
vendor suggests a "in and out window" workflow versus a "bank teller" model then they should
explain why.
4.7. Medical Device STIG
The vendor shall be compliant with all of the requirements the Defense Information Systems
Agency (DISA) medical device Security Technical Implementation Guide (STIG).

5. SYSTEM REQUIREMENTS

5.1. System Interfaces
The system shall use the latest HL-7 protocol(s) or other industry standards used in the DoD. The
system shall be capable of interfacing with other commercially available pharmacy systems (i.e.
robotics) or other AIS.
5.2. WFMS Data Accessibility Requirement
All data captured and stored by the WFMS shall be open to external analysis and available for full
downloads in an ODBC compliant unencrypted format. Any backup database shall be automated, at
a user defined schedule, and be fully accessible for review of data content and extraction.

All data captured and used by the WFMS during its function at Navy pharmacies belongs to the
hospital and shall be fully accessible by the hospital for downloads, backups, or extracts. In
addition a full data dictionary of the tables, fields, formats, and definitions for all the databases
accessed or used by the WFMS for operation of the system shall be provided. This requirement
does not exclude the need for reporting described in this document but is an additional
requirement so that ad hoc reporting, analysis, and system simulation can be performed by the
hospital or their contractors
                                                                                      N62645-11-R-0027

                                                                                           Page 24 of 93

Required data accessibility includes but is not limited to: each and every processing time stamp
captured by the automation, drug information including cell locations, inventories, and
classifications, patient information, script details, audit and record edits, all details related to the
movement of prescription orders through centralized process, all personnel scans and information
captured on staff involved during processing of the script, and any other information captured by
the system during the receipt, filling, processing, or dispensing of the script.
5.3. WFMS Interface to CHCS
All order information shall be sent from CHCS to the WFMS. This is a one-way interface from CHCS
to the WFMS. It is the responsibility of a WFMS to capture and decode the file from CHCS prior to
giving an acknowledgement back to CHCS.
       5.3.1. Provide audible/visual signal if Interface is Down
The interface to CHCS is a one-way interface (all data flow is from CHCS to the WFMS software).
This provides the opportunity for the interface to go down which prevents CHCS from passing
down orders. If CHCS does not immediately recognize the loss of the interface, data may continue
to be sent but the data is not received by the WFMS software. As a minimum, a timer shall be
utilized to indicate the amount of time since receipt of data from CHCS. If the amount of time
exceeds the configurable value, a visible indicator should be activated to alert the pharmacy that
files are not being received. A record of the down times shall be available to help personnel track
down any files that have not been transferred while the interface was down.
       5.3.2. Operating when Interface to Host is Down
Loss of the interface with CHCS shall not impede the system from continuing to fill orders until all
orders that have been transferred have been filled.
       5.3.3. Automatically Recover from Downed Interface
The WFMS shall be capable of automatically coordinating recovering from a downed interface
without requiring manual intervention. A log of the time the interface is re-established shall be
maintained to help enable pharmacy personnel to recover any orders that may have not been
received.

As part of the automatic recovery, the WFMS shall be capable of recognizing and consolidating any
“duplicate” orders. The order in the WFMS shall be updated to contain the most complete record.
If an Rx from an order was missed due to the interface going down and the order was manually re-
sent from CHCS, the WFMS shall add the missed Rx to the order. If the order has already been
dispensed and issued, this order shall be referenced in a log as an incomplete order. If the order is
in-process but not yet issued to the customer, the missing Rx shall either be dispensed (order not
yet processed) or a QA flag shall be set for this order so that the checking Pharmacist is alerted to
the missing Rx.
       5.3.4. Capability to Send a message to Host when Order is Complete
                                                                                    N62645-11-R-0027

                                                                                         Page 25 of 93

At the present time, CHCS expects an acknowledgement back from the WFMS upon receipt of an
order. No other communication from WFMS to CHCS is permissible at this time. Although the
“dispensed” information cannot be sent back at this time, the WFMS shall be capable of sending a
message to the host system that an order has been dispensed to a patient. This message shall
contain dispensed medical information (message format and interface would be determined if this
functionality is added to CHCS). Although the specific information to be sent to CHCS for each
order has not been established at this time, the WFMS shall be capable of sending all the specific
dispensing information associated with an order. This may include but is not limited to Rx
numbers, drugs numbers, NDC numbers, lot/expiry information, date/times and Pharmacist of
record for the order.
5.4. Response Time to Terminal Input
The WFMS provided shall be capable of operating with reports running in the background and still
be responsive to all manual stations that interface with an order. WFMS shall respond to
terminal/scanner inputs within 1/2 second or less when the database has 200% of the daily
expected numbers of orders present. In addition, from the time of a verification scan of an NDC, the
printer shall be capable of initiating an Rx label print within one second.

Handheld terminals, including those utilized at the PV station, shall respond in the same time frame
as hard wired terminals. All wireless components shall need to comply with the latest DoD and
DoN Security Technical Information Guides.
5.5. Handle Compounding Rx’s
A means is required to handle dispensing of Rx’s that include a locally compounded item for
dispensing. The system shall have the capability to enter and maintain locally generated NDC
numbers. The system shall be capable of printing a label for the compounded items that may be
prepared ahead of time. This type of item shall be tracked by the WFMS the same as a RTS or pre-
pack.

The database for the locally entered NDC’s shall be separate from the NDC table being maintained
by the contractor. Adding and subtracting from this database shall only be done by pharmacy
personnel.
5.6. Known Drug Shortages
If there is an inadequate quantity of a specific drug within the pharmacy as required for the order,
the order should be scheduled as though the drug is present. This shall result in the order reaching
PV and one of the Rx’s not being filled. A decision shall be made at the PV station to issue the order
to the customer minus the drug or hold the order until the drug is received at the pharmacy. The
WFMS shall be capable of supporting either decision by the PV Pharmacist.
5.7. Physically Large Orders
The system shall be capable of processing physically large orders which would require separation
into separate portions. The WFMS shall be capable of processing such orders while associating the
two, or more, portions with a single order as well as provide each portion’s location in the process.
The WFMS shall clearly indicate to the operator at the PV station that an order is part of a multiple
portion order, upon receipt of the first portion of the order.
5.8. Verification Images of Dispensed Drugs
                                                                                     N62645-11-R-0027

                                                                                          Page 26 of 93

The system shall provide imaging capability for applicable drug products. For packaged items or
non-oral solid dosage forms, picture of packaging as provided by manufacturer shall be provided.
An image database shall be provided that shall be capable of displaying an image of the dispensed
drug. This image should be displayed during dispensing, PV, automated counter cell refill and
stocking functions. For tablets, an image of two sides of the tablet shall be displayed and for unit of
use items, an image of the manufacturer’s package shall be displayed. The monitors used for
dispensing, PV, automated counter refill and restocking shall be color capable as to display a
realistic image (correct colors).
5.9. Hardcopy Prescriptions
As part of the intake process, one or more induction windows shall be equipped with the capability
to scan a paper script. The scanner and supporting equipment shall be provided by the contractor
as part of the overall system. In addition to imaging a paper script, some scripts shall be
transferred into the WFMS as electronic files. The capability to print a paper copy of this script
shall be provided. Hardcopy prescriptions shall be retained in memory and accessible from all
automation consoles and shall be capable of producing on screen and printable copies of the
scanned hardcopy for a period of at least 3 years.
5.10.   Support Dispensing Pre-Packs or Manufacturer Put-Ups
The WFMS shall have the capability to utilize pre-packs and manufacturer’s containers in
conjunction with the drug being located in the automatic counting machine. The system shall
provide the ability to generate barcodes for locally pre-packed items and the unique barcode
created shall be able to be utilized in the processing of prescriptions. Depending on the count of
the Pre-Packs/ Manufacturer’s Put-Up and the required count for the order, the WFMS shall be
capable of utilizing both the automatic counts and Pre-Packs. In all cases involving a combination
of pre-packs and/or manufacturer’s put-ups and ACM dispensed drugs, the minimum number of
bottles required to contain the Rx shall be utilized. For orders that require only pre-packs or
manufacture’s put-ups (entire Rx is dispensed from a manual station), the bottle count may not be
the minimum.

The WFMS shall also support producing pre-packs during off-shift that would function the same as
the manufacturer’s bottle described above. The pre-packs bottle bar code should link to the
date/time, lot number and expiry date the pre-packs bottle was produced.
5.11.   Supporting Return-to-Stock (RTS)
It is anticipated that the ACM shall occasionally have count errors or run short of drugs (not be
capable of completing a count). When this occurs, the system shall be capable of labeling this bottle
using a pre-defined Return-to-Stock (RTS) label. This bottle would be diverted from the normal
flow and shall be able to be used for future use, such as re-introduction back into the counting cells,
typically during the counter refill cycle. The bar code on the RTS bottle shall be linked to the
date/time the bottle was produced, the NDC, the count quantity in the bottle, the lot code and
expiry date. During replenishment of the counting cells, a scan of this bottle shall be equivalent of
scanning the NDC of a normal resupply bottle, except that the lot code, expiry date and quantity
shall not be requested. The WFMS shall be capable of handling RTS bottles with an unknown
quantity of tablets.
5.12.   Relate Generically Equivalent Drugs
                                                                                       N62645-11-R-0027

                                                                                            Page 27 of 93

Many NDC’s exist for the same drug/strength combination. The system shall be capable of
recognizing these equivalents, based on a peer-reviewed and validated commercial product
reference database, and substituting to utilize the actual drug in stock. If more than one equivalent
drug is in stock, the oldest is to be utilized first if there is a choice. Various manufacturers’ put-ups
of the same drug, generically equivalent drugs (from the same or different manufacturers) shall be
treated in the same manner.
5.13.   System Updates
There shall be a means for the contractor to keep the various databases current over the life of the
system (the period of the service contract). Updates shall occur after informing and receiving
approval from the appropriate Navy authority such as the NAVMISSA PM and or local commander.
Upload of approved updates should occur during an off shift period when the system is not in use.
A means to accomplish this update is to be provided as part of the quote being provided.
5.14.   System Redundancy
The contractor shall provide a fully redundant computer system. A minimum of two servers shall
be required that can be automatically switched between the servers or rapidly be changed from
one server to the other if full automation is not practical (port ID may have to be manually set up).
In addition, a RAID 1 database shall be utilized that provides 100% redundancy should a disk drive
fail. The computer system should be available 99.99% of the time based on any system hardware
failures.

An assessment of each specific site is to be made to determine if all the servers can be virtualized
by operating on existing site servers and utilize the existing UPS.

A 20 minute minimum UPS shall be provided for the computer system to enable the backup
generators to come on-line without an interruption in operations. The UPS shall also power the
client PC’s. The ACM shall be fully recoverable after a power outage with at most, 3-4 Rx’s
requiring an RTS bottle or also be included on the UPS.
6. CONVEYOR REQUIREMENTS
The Government has not identified any solution that would not incorporate a conveyance system.
However, an offeror may propose an alternative solution capable of meeting the same functional
capabilities of a conveyance system. A conveyor system would be responsible for moving orders
through the system. The WFMS shall determine the next stop for the order and shall direct the
conveyance system to accomplish this move.

The conveyor system shall be customized for each specific site based on an approved site layout.
The conveyor system shall be customized for the specific site but shall be composed of the various
items including but not limited to:

       Straight run sections

       90 and 180 degree turns as well as other angled turns and angle changes

       Inclines and declines

       Guard Rails
                                                                                    N62645-11-R-0027

                                                                                         Page 28 of 93

      Transfers

      Scanners & photocells

      Bladder accumulation

      Physical stops

The design proposed shall be based on avoiding potentials for order jamming. Filled orders shall
terminate at PV and not be able to continue to an issue window.

Each dispensing station shall have a buffer area preceding it. Number orders capable of being held
in this buffer area shall depend on the space constraints of the pharmacy.

Conveyor transfer shall be provided at all merge locations along the conveyor system. Order
accumulation areas (bladders) shall be provided shall be part of the conveyor system. Bladder
areas shall not allow orders to be dislodged from the conveyor. Each bladder area shall have
sensors to determine when the bladder stop can release the next tote.

Each fill station (ACM and manual) shall have a reader to indentify which order is in position to be
filled and relay order dispensing information to the fill station for fulfillment.

Stops shall be utilized at the PV stations to enable the Pharmacist to easily remove a tote. All
conveyor drives shall utilize Variable Frequency Drives (VFD’s) to the conveyor system to operate
at various speeds. The conveyor system shall be capable of speeds between 40 and 80 FPM.

An incline/decline angle shall be selected that is sufficiently steep to minimize the run of conveyor
required to accomplish the elevation change.
7. DESIGN AND FABRICATION REQUIREMENTS
7.1. Safety Standards and Codes
All equipment shall conform to appropriate safety requirements. Equipment shall be designed in
conformance with the current version of the following standards:

Occupational Safety and Health Act Regulations (OSHA)

American National Standards Association (ANSI)

American Society of Mechanical Engineers (ASME)

NFPA 79: Electrical Standard for Industrial Machinery

National Electrical Code (NEC)

National Electrical Manufacturers Association (NEMA) or equivalent.

All Applicable Federal, State and Local Codes, Laws and Regulations

7.2. Quality Requirements
                                                                                   N62645-11-R-0027

                                                                                        Page 29 of 93

The Equipment Contractor shall maintain an in-process and end-item quality control program to
ensure shipments to the Government do not include defective or non-conforming items.
7.3. Calibration
The Contractor shall provide proof of calibration status.

The Contractor shall provide recommended calibration method and frequency.

Devices and/or instruments requiring calibration shall be located within the System in such a way
that they can be easily re-calibrated in future.
7.4. Guarding
The Contractor is responsible for all equipment guards or barriers required to protect people from
the operation of the equipment. All sprockets, chains, gears and belts subject to personnel contact
shall be fully enclosed in readily removable split-type guards. All guards shall be easily removable
for repairs and maintenance.

All equipment guarding shall conform to current OSHA requirements and ANSI/ASME Safety
Standard For Conveyors and Related Equipment B20.1 and ANSI/ASME Standard For Mechanical
Power Transmission Apparatus B15.1.
7.5. Supports and Connectors
All equipment or equipment supports shall be supported from the floor or columns. No equipment
shall be ceiling hung. Major component assemblies are to be connected using a positive connector
employing a bolt and locking device.

7.6. Mechanical Requirements
     The system shall not damage either the product or system components in any mode of
       operation.
     The system shall be serviceable. Mechanical and electrical design shall be of a modular
       configuration for ease of maintenance and repair. Motors and drives shall be mounted to
       allow for primary access from planned operator areas.
     All equipment shall operate at or below 80 dBA, measured at the operators work station or
       at the nearest work station, traffic aisle or pedestrian access.
     All equipment shall be sized for receipt through doors 3 feet wide by 80 inches high.
     The minimum factor of safety base yield strength shall be 1.65.
     The System shall be vertically adjustable (at least ± 2”) in order to allow for leveling.
     Nameplates shall be provided that identify starters, switches, push-buttons, pilot lights,
       relays, motors (per NEMA Standard MG-1, Part 10) and other components and mounted
       immediately above or below the device.
     Critical detection systems shall be designed so they cannot be bypassed in normal run
       mode.
     Part numbers shall be indelibly marked on all parts.
7.7. Material Requirements
     All materials shall be non-toxic.
     All material and equipment shall be new, unless otherwise specified, and any procured
       source material or components shall be the product of a manufacturer with ISO
       certification and whose products are approved by a nationally recognized testing
       laboratory.
                                                                                      N62645-11-R-0027

                                                                                            Page 30 of 93

       All cuts, edges, holes and assembles are to be free of burrs and sharp edges. All exposed
        corners of metal members shall be rounded and smooth to remove accident hazards.
       After installation, components shall be field painted as described above to cover any areas
        that have been rubbed, scratched, blemished, etc. during shipment and/or installation.
       All exposed surfaces of non-stainless type steel or other corrosive materials shall be
        painted with corrosion resistant paint or anodized.
       All bolted connections shall include lock washers or approved locking hardware.
       No bolt heads or other projections shall protrude in such a way as to possibly injury staff,
        snag or hinder the movement of pallets, cartons or create a hazard for proper maintenance
        of these fasteners.

7.8. Sensor Mounting
All sensors (proximity switches, etc.) shall be adequately secured to prevent movement or
loosening by vibration.
7.9. Labeling
All equipment switches, motors, valves, regulators and etc shall be clearly labeled to identify the
associated function for reference to maintenance and operator manuals. Labels shall be
permanently attached to, or near, the device.
7.10.   Welding
All welding shall fully comply with the requirements of the American Welding Society's codes as
amended to date. All welding shall be under direct supervision of qualified personnel. Welding
operators shall have been qualified within twelve (12) months prior to work on this project, except
that personnel continuously employed as welders shall be accepted on the basis of satisfactory
reports dated not more than two years prior to project start. Safety regulations and fire codes shall
be stringently adhered to. All welds on product contact surfaces shall be continuous and ground
smooth.
7.11.   Touch Up
After installation, components shall be cleaned and any areas that have scratches, blemishes or the
finish rubbed off shall be touched up to match the original paint quality.
7.12.   Power Distribution
The vendor shall be responsible for running all power lines required for the system. If necessary,
the vendor is responsible for obtaining all required permits. The vendor shall be responsible for
submitting power and compressed air requirements to the project engineer for approval during the
process design review and approval.
7.13.   Equipment Control Requirements

        7.13.1. Location of Controls
All starting/stopping controls shall be within easy reach of the operator. If there are positions for
more than one operator, an emergency stop shall be provided in a location easily accessible for
each position.

All controls shall be clearly identified as to function and protected against accidental activation.
                                                                                            N62645-11-R-0027

                                                                                                Page 31 of 93

Set-up controls shall be located and mounted such that they do not require the operator to reach
past rotating or moving elements or work in progress to operator the controls.
        7.13.2. Emergency Stop
Emergency Stop switches shall be provided. They shall be easy to identify and prevent unintended
activation.



In the event where there is a risk of inflicting injures to the operator or giving damage to the
machine, the system shall be capable of being put into an emergency stop state. Emergency stop
state shall be defined as: Stop the motion of the equipment as fast as possible. All sources of energy
in the equipment in such as electrical, pneumatic, hydraulic, gravity and inertia energies shall be
disconnected and said energies dumped in the emergency stop state.

As in the event of a utility failure, the System shall protect in the following priority:

Personnel

Equipment

Product

All orders in-process and being worked on by a station within the emergency stop zone shall
automatically be rejected upon restart. Parts in queue either prior to or after the part being
worked on by the station shall not be a reject.
        7.13.3. Zone Stop
The system shall be capable of zone stops such that all sources of energy to a particular “zone” of
the system shall be disconnected and dumped. If the equipment’s design or size, or if the specific
site does not necessitate the implementation of separate zone stop switches, emergency stop
switches shall still be provided.
        7.13.4. Cycle Stop
System shall be capable of a "Cycle Stop". A cycle stop shall allow the system to execute a
controlled stop. A cycle stop shall allow devices to continue to finish their sequence, returning to a
known ‘home’ position before stopping. No power shall be removed at the end of the cycle stop.

All orders in-process and being worked on by a station within the emergency stop zone shall
automatically be rejected upon restart. Parts in queue either prior to or after the part being
worked on by the station shall not be a reject.
        7.13.5. Modes of Control
There shall be 2 modes of operation; Production and Manual. By default, the System shall power up
in Production Mode.
                7.13.5.1.1.      Production Mode
The System shall operate automatically with intervention by the Operator only for material
replenishment and/or in the event of System stoppage.
                                                                                  N62645-11-R-0027

                                                                                          Page 32 of 93

       Production mode shall be the normal operating mode for the System

       All product required subsystems shall be enabled.

       Critical alarms and faults shall remove the system from the Production Mode and place it in
        the Stop Mode. Completion of the cycle shall be inhibited if machine integrity may be
        compromised.
               7.13.5.1.2.    Manual Mode
All subsystems that were isolated or disabled while in Manual mode shall be reset and enabled
when Production mode resumes.

Manual mode shall be the operating mode used by the technical staff during set-up, changeover,
and/or normal troubleshooting.

Manual mode shall allow for the isolation of subsystems so that the System can operate without
them.
        7.13.6. Alarms and Informational Messages
Any error message or alarm shall always be indicated by means of a text display and a flashing LED
or lamp when appropriate.

The System shall include both audible and visual features to acknowledge alarm conditions and
system status. These shall include alarms and tri or quad-color light towers.
               7.13.6.1.1.    Informational Messages/ Operator Alert
The system shall identify System status through appropriate messaging. Informational messages
shall not result in System stoppage. Informational messages shall be acknowledged by the Operator
and/or Technician. Examples of informational messages are as follows:

       Low component supply

       Low battery

       Low air pressure

       High level infeed
7.14.   Data Security
Qualified personnel shall be able to access the control software to modify machine control
parameters, process set points, change critical/informational messages, or other parameters.
Access shall be determined by role based security.
7.15.   Auxiliary Outlets
Contractor shall provide a grounded, 115 VAC, 15 AMP, convenience outlet in each control cabinet.
Power shall be sourced from the primary side of the control cabinet disconnect.
7.16.   Disconnects
Each motor control cabinet shall have a three-phase disconnect with lockout capability.
                                                                                    N62645-11-R-0027

                                                                                         Page 33 of 93

7.17.   Wiring
The system shall be designed to permit implementation and usage of local power for Navy Medical
Treatment Facilities at a minimum in the following countries/locations:

       United States 110 VAC 60 Hz

       Italy 110 VAC 50Hz, 220 VAC 50 Hz

       Spain 115 VAC 60 Hz

       Japan 100 VAC 60 Hz, 100 VAC 50 Hz

       Bahrain 110 VAC 50 Hz, 220 VAC 50 Hz

       Guam 110 VAC 60 Hz
        7.17.1. Grounding
All wiring shall include a white neutral and a green ground. The ground wire shall daisy chain to all
components and connects to "earth" ground at a single point.
        7.17.2. Terminations
Terminations shall be made in control cabinets or junction boxes on terminal blocks. No more than
two wires shall be connected to any single terminal point. Splices shall not be made inside wire
ways or conduits. Wiring shall be installed (where ever possible) such that the disconnection and
removal of each individual instrument or electrical device can be accomplished without removal or
significant distortion of wiring bundles, conduits, etc.
        7.17.3. Protection
Conductors and cable within wire ways or conduits shall be protected from mechanical damage or
abrasion. Conductors leaving wire ways, conduits, junction boxes or control cabinets shall have
proper strain relief devices.

Electrical wiring that connects to moving members shall be adequately protected from wear and
kinking by means of flexible plastic track assemblies or other means.

All jacketed cable shall be run in conduit or wire way. Cable exposure shall be kept to a practical
minimum. Unjacketed wire shall not be used.
        7.17.4. Wire Color Codes
Electrical power and control wiring (not including communication lines) shall follow accepted
standard color-coding guidelines.
        7.17.5. AC and DC Wiring Separation
AC and DC wiring shall have separate wire way, conduit, or partitioned wire way.
        7.17.6. Spare Wire
                                                                                     N62645-11-R-0027

                                                                                          Page 34 of 93

Spare wires of the same gauge, color and type, as the active wires shall be provided. The number of
spare wires shall be, within practical limits, between 15 and 20 percent of the number of active
wires. Each wire shall be long enough to reach any point within the box or cabinet where located.
        7.17.7. Conduit
Conduit sizes and capacities shall adhere to the National Electric Code.
7.18.   System Installation and Cabinet Construction
       Any and all cabinets or panels shall conform to NFPA 79, Electrical Standard for Industrial
        Machinery.
       Any and all cabinets or panels shall be of stainless steel construction with either unitized or
        modular assembly in conformance with NEMA 12 standards unless a greater standard is
        required. The cabinet shall have locking type door handles and/or latches.
       Any and all cabinets or panels, other than field terminal cabinets, shall have an externally
        operated disconnect capable of disconnecting all electrical power to the cabinet by means
        of a circuit breaker, molded case switch or fused disconnect switch. These devices need to
        be guarded in accordance with NFPA 79. Enclosure doors shall have key or tool-operated
        latches.
       The primary power supply for the project shall be 220 or 480 VAC
        7.18.1. Contractors and Power Switching Devices
The following general requirements should be followed with regard to contactors and power
switching devices:

       Should comply with UL, IEC, etc. standards
        7.18.2. General Wire and Wiring Conventions
     Wires should be clearly labeled at all termination points
     Conductors should be stranded
     Conductors of higher than 120 volts should be isolated from low voltage conductors and
        commons by separate conduit or shielding
     Wiring troughs should be routed to any branch equipment where more control conductors
        are required than shall fit in a single rigid conduit
     The use of wire ties to support wire should be used in routing and within 6 inches of the
        control device to protect leads from incidental damage
     All equipment components not permanently connected (welded) should incorporate a
        termination enclosure. In addition, all control devices should be terminated in the local
        enclosure to facilitate ease of disconnection for relocation.
     Devices requiring maintenance or replacement should be mounted and terminated in a
        manner to accommodate rapid removal and reinstallation
8. INSTALLATION REQUIREMENTS
8.1. Installation and Technical Support
The Contractor shall be responsible for all assembly and installation to include site modifications.
This may include removal and/or trade-in of the currently installed equipment.
Vendors shall perform site renovations related to the installation and use of the proposed solution
such as electrical routing, patch work and cosmetic clean-up work after installation. Vendors may
only propose modifications to a pharmacy's floor plan if it directly relates to proposed solution's
ability to function (i.e. addition/subtraction of pharmacy patient windows). Vendors shall not
                                                                                    N62645-11-R-0027

                                                                                         Page 35 of 93

propose or perform any renovations to load bearing structures or renovations that will require
asbestos abatement.

If the Equipment Contractor uses another Installation Contractor, the contractor shall still be
responsible to provide technical support during installation. Any modifications to the existing
space shall be coordinated and approved by the Facilities Management Office before any work may
commence.

Installation will be evaluated at the delivery order level.

Permits

The Contractor shall be responsible for obtaining all permits, approvals, paying all fees and
complying with all applicable governmental statutes, codes and regulations except as otherwise
specified by the Government.

Goods manufactured or supplied by Contractor shall comply with all applicable codes, rules,
orders, ordinances, regulations or requirements issued there under, and shall indemnify
Government against any damages by reason of violations of this paragraph.
8.2. Use of Premises
The Contractor shall confine operations and those of any subcontractors to the project area of the
site. Contractor shall limit the use of the premises for work and for storage, to allow for work by
other Contractors and construction personnel on the project. Contractor shall coordinate the use
of the premises with the Government or his designated representative. All employees of the
Contractor and his subcontractors shall be restricted to the project area. They shall not enter the
building except as required to complete the work covered by this project.

The Government shall at all times have access to the Project wherever it is in preparation location
and progress. The Equipment Contractor shall provide facilities for such access inspections and
otherwise as Government deems reasonably necessary.

The Contractor shall supervise and direct the project, using his best skill and attention and shall be
solely responsible for all construction means, methods, techniques, sequences and procedures and
for coordinating all portions of the project under Contract. The Contractor shall be responsible to
the Government for the acts and omissions of Contractor employees, subcontractors and their
agents and employees, and other persons performing any of the work under a contract with the
Contractor.

The Contractor shall enforce strict discipline and good order among Contractor employees and
shall not employ on the project any unfit person or anyone not skilled in the task assigned to him.

The Contractor shall supply the Government with the names of all personnel to be admitted to the
job site. Contractor’s personnel shall follow security procedures (name tags, check-in, etc) as
directed by the Government. Contractor's personnel shall enter and exit at locations designated by
the Government. The Contractor's employees shall confine themselves to the immediate work area
on the site. No cameras shall be allowed on site.
                                                                                   N62645-11-R-0027

                                                                                        Page 36 of 93

The contractor shall supply office and telephone services for their personnel during installation.
The Contractor may be required to separate off the work area via visible barriers or some other
means of containment. No smoking shall be permitted in any building.
8.3. Protection of Persons and Property
The Contractor shall be responsible for initiating, maintaining a safe work environment and
supervising all safety precautions and programs in connection with the Project. The Contractor
shall be responsible for ensuring that the Contractor's employees, subcontractors, and agents are
furnished with proper safety equipment and that all equipment and work methods are in complete
conformance to National, State and local laws and the Government's standard safety procedures.
8.4. Working Hours
All work at job site shall be performed by indicated labor under the proper supervision of a
qualified representative of the Equipment Contractor. Regularly scheduled hours of work shall be
agreed upon by both the Government and the Equipment Contractor. The purchased systems shall
be installed in operating pharmacies. Installation shall not require the pharmacy to be shut down.
Working during non-operating hours and weekends may be required. Work areas shall be
identified, and readied for use based on a project completion schedule submitted by the contractor.
8.5. Delivery and Unloading
The Contractor shall be responsible to load the components on the delivery carrier for unloading at
facility. An assessment shall be made at the particular site to verify the maximum entry opening.
The Contractor shall provide an estimate of the number of truckloads to be delivered. Site storage
of trailers shall be planned and scheduled with the Government. The contractor shall provide own
forklift equipment and other wheeled, lift equipment as required for installation and unloading.
Contractor shall take measures to avoid any damage to or marks upon the floor caused by
equipment provided or used in the project.
8.6. Site Cleanliness
The Contractor shall be responsible for overall cleanliness of the work area during installation and
shall keep the premises free from accumulation of waste material or rubbish caused by their
operations as well as tools, construction equipment, machinery and surplus materials. The
Contractor shall clean installation area daily, removing the collected materials to an approved
dumpsite. Combustible materials shall not be allowed to accumulate and shall be removed from
the installation site daily. All working areas shall be broom cleaned regularly. If the Contractor
fails to clean up at the completion of the workday, the Government may do so and the cost thereof
shall be charged to the Contractor.
8.7. Site Storage
The Contractor shall store material, equipment and tools only at locations designated by the
Government and shall not obstruct any roads, aisles, doors or passageways. Care shall be taken to
avoid the direct placement of materials to the floor surface. Sufficient packaging or dunnage
should be provided so as to prevent damage, marring, or soiling of these materials while in storage.
Government assumes no responsibility for losses due to theft of Contractor's stored materials.
8.8. Trash Removal
                                                                                    N62645-11-R-0027

                                                                                         Page 37 of 93

The Contractor shall provide containers for all their collection and transfer of materials and trash.
The Contractor is responsible for all trash disposal. The vendor shall be responsible for the daily
cleanup of the work area. The vendor shall provide dumpsters for the removal of all trash from the
site.
9. DOCUMENTATION

9.1. Pre-Installation Drawings and Specifications
The Equipment Contractor shall submit to the Government for approval, with such promptness as
to cause no delay in work, all shop drawings and schedules required for the fabrication and
installation work. Installation Drawings (footprints, locations, services, wire ways, etc.) shall be
provided by the Contractor at least four weeks prior to scheduled installation. The Government
shall review and, if acceptable, approve the drawings within one week.

The Equipment Contractor shall furnish one (1) clear, legible set of reproducible drawings for
approval, along with brochures, descriptive literature, footprint dimensions (H x W x L) for all
components of system, and material samples, where necessary. These drawings and component
schedules shall be complete and detailed.

The Equipment Contractor shall verify all drawings before performing on the contract and shall be
responsible for any errors that might have been avoided. Further, the Equipment Contractor shall
check all drawings, figures, and Specifications immediately upon their receipt. The Government's
approval of such drawings or schedules shall not be construed as a complete check, but shall
indicate only that the general method of construction and detailing is satisfactory. Approval of
such drawings shall not relieve the Equipment Contractor of responsibility for the dimensions and
design of adequate connections, details, and satisfactory construction.
9.2. Drawing Submittal Requirements
      Revisions to Conceptual Design if deemed necessary.

      Mechanical Design Drawings

      Electrical Layout, Wiring Diagrams and Schematics

      Electrical Field Component Layout Drawings

      Pneumatic and Hydraulic Piping Diagrams and Schematics

      Installation Drawings (footprints, services, conduits, etc.)

      Equipment fabrication Drawings. The Contractor shall submit three complete sets of
       fabrication and installation drawings according to the project schedule.

      As Installed (As Constructed) Drawings
9.3. As-Constructed Drawings
                                                                                   N62645-11-R-0027

                                                                                        Page 38 of 93

Following installation of the equipment furnished under the contract, the Equipment Contractor
shall furnish a complete set of reproducible drawings, indicating the "as-constructed" condition of
the equipment layouts, electrical layouts and diagrams, piping layouts, etc., as applicable. Layouts
shall be accompanied by an associated electronic Auto Cad file. The file format shall be AutoCAD
Version 2010. The Contractor shall submit two sets of "as installed" reproducible drawings within
two weeks after operational start up.
9.4. Required Final Documentation
The Equipment Contractor shall be responsible for collecting, identifying, and collating the
following materials regarding the equipment furnished under the contract, and shall deliver two
(2) copies to the Government for review of correctness, and shall then deliver two complete and
final sets to the Government. This includes, but is not limited to, all "As Constructed" drawings,
diagrams, manuals, operating instructions, parts lists, inspection lists, reports and warranties
necessary to complete the contract.
The above materials shall be furnished as applicable for each type of fixed equipment furnished
under the contract. These materials to be supplied in a hard cover ring binder, properly indexed,
for ready future reference
9.5. Maintenance Instructions and Manuals
The Equipment Contractor shall furnish a complete set of documentation regarding the
recommended maintenance procedures related to the care of the equipment. Recommended
preventative maintenance schedules, inspection frequency, common repair procedures and
instructions shall be included. Operating instructions and maintenance materials shall contain the
following information:

      Description of operating procedures (including start-up and shut-down procedures).

      System interlocks and emergency stop conditions and recovery.

      Description of any error codes and diagnostic routines.

      Description of operation for all operator interface terminals.

      Normal preventative maintenance procedures to be performed by Government and tools
       required. Schedule and frequency of required equipment maintenance.

      Catalog and specification data regarding all equipment and hardware furnished.

      Operating Instructions and training aids.

The Equipment Contractor shall furnish three (3) sets of hardcopy and electronic manuals,
including catalog information covering all purchases and/or subcontractor items supplied under
the contract. Electronic copies of manuals shall be capable of being duplicated. These manuals and
lists shall be submitted thirty (30) days before the scheduled completion date.

10. GOVERNMENT TRAINING
10.1. User Training
                                                                                   N62645-11-R-0027

                                                                                        Page 39 of 93

The Contractor shall develop a training program and supply materials and labor required to ensure
that the Government achieves the level of skill required to operate and maintain the equipment at
the throughput and operating levels required by this document. The program shall be designed so
that the Government's personnel are adequately prepared to assume complete operation of the
equipment at the successful completion of acceptance testing. Provisions shall be made to allow
for the advance approval by the Government of the training program.

Government anticipates a professional training program consisting of adequate visual aids,
structured classes, group discussion and visits to other sites as determined appropriate. (Such
visits shall be at Government’s expense)

The Contractor shall provide an adequate number of English speaking personnel who maintain
sufficient management, technical and communications skills to provide the Government's
personnel with the skill levels necessary to successfully operate the equipment. Contractor
personnel assigned to conduct training shall be approved in advance by Government.

All training shall take place at the Government's facility with the exception of Contractor facility
sessions as desired by Government. The Government shall provide adequate space and visual aid
equipment for formal training as required by the Contractor.

All training manuals, documentation and aids shall become the property of the Government and be
used at the Government's discretion for future training of other personnel. The Government
reserves the right to record any training sessions and use these materials as required.

The Contractor shall make recommendations concerning technical or general training programs
available through other organizations that may benefit the Government.

Contractor shall plan that the typical recipient of operator training has a relatively low level of
system knowledge and an average ability to learn. All trainees shall have ability to follow verbal
and written instructions.

Supervisory personnel shall be appointed from Government's existing operations and management
design team. Training shall be designed to familiarize the Government's management with the
total system operation, high level maintenance requirements, control and systems integration
methodology necessary to effectively trouble shoot and plan day to day operations. Start up and
shutdown operating procedures and alarm responses shall be included in such training.
10.2.   Control System Training
It is probable that the Government shall designate one or more key individuals to become
intimately involved with the system. While this may require technical courses at other control
device manufacturer's training facilities at the Government's expense, it may require extended
visits to the Contractor's facility. The Contractor is to make his facility available to the
Government's personnel to support this training effort. Further, the Contractor is to recommend
dates, times and durations for facility visits by Government's personnel at key milestones during
the control system development.
11. SYSTEM WARRANTY, RELIABILITY, MAINTAINABILITY AND SUPPORT
11.1. Warranty
                                                                                   N62645-11-R-0027

                                                                                        Page 40 of 93

“Contractor” warranty shall at a minimum warrant and implies that the items delivered hereunder
are merchantable, fit for use for the particular purpose and shall be free from defects in materials
and workmanship for a period of not less than one year from the date of installation. “Contractor”
shall replace all parts found defective within the period, with the cost of replacement, including
labor and shipping charges, to be borne by “Contractor” This warranty shall cover at a minimum:

       Equipment manufactured by ““Contractor”

       Equipment not manufactured by “Contractor”, and

       Software provided by “Contractor”

       Robotic Equipment and Software provided by “Contractor”
11.2.   Customer Support
Customer Support shall be provided at no cost during the initial warranty period, for

       Equipment manufactured by “Contractor”,

       Equipment not manufactured by “Contractor”, and

       Software provided by “Contractor”

       Robotic Equipment and Software provided by “Contractor”

This support shall include updates to software, drug database, antivirus, and operating system, also
at no cost during the initial warranty period.
11.3.   Customer Technical Support Program
The “Contractor” shall provide a complete description of their Service Level Agreement (SLA) and
Customer Support Plan. The following categories are the minimum requirements. For all described
services, the “Contractor” shall provide Specific Measurable Attainable Repeatable and Time
(SMART) oriented customer support deliverables. For every deliverable, the “Contractor” shall
provide the method for validating and evaluating their performance for quality. The “Contractor”
shall provide all remote support and maintenance to include Information Assurance (IA) through
the DoD business to business (B2B) gateway prior to installation and shall verify end to end
connectivity before delivery and attempting to install any equipment. If the DoD or Navy migrates
to another commercial partner gateway besides the B2B gateway, the “Contractor” shall maintain a
support connection on this new gateway. All remote support shall be in accordance with the DISA
Medical Device Security Technical Implementation Guide (STIG) as well as other DoD or Navy
requirements for customer support.
        11.3.1. Telephone Support
The “Contractor” shall provide telephone support seven (7) days per week, twenty-four (24) hours
per day through a toll free telephone number under the provisions of the Warranty. The
“Contractor” shall provide a full description for their manner of accomplishing this call response
requirement.
                                                                                        N62645-11-R-0027

                                                                                             Page 41 of 93

“Contractor” shall maintain a trained staff of Technicians that respond to Customer telephone calls,
faxes or e-mails regarding equipment, software, training, calibrations, etc., (“Call” or “Calls”). The
“Contractor” shall provide their method of call routing and customer tier level support to include
any tracking mechanisms and result resolution methods to ensure all calls are closed properly. The
“Contractor” shall provide a detailed explanation of how support for customers outside of the
continental United States (OCONUS) shall be provided if different from Continental Unites States
(CONUS). The goal for resolution via remote support that the “Contractor” is depicted in Error!
Reference source not found.Error! Reference source not found.. The “Contractor” shall provide
a call escalation plan that any facility can use in the event that they feel they need a more rapid
response. This escalation plan shall contain procedures and contacts for contacting senior
customer service representatives to include cell phone or other points of contact.

In the event the “Contractor” is unable to resolve an issue after the initial call, the “Contractor” shall
provide adequate follow-up, tracked by providing Company’s Tier level support POC, date and time
of subsequent calls, progress made, and resolution. Issues not resolved within 7 working days shall
be reported to NAVMISSA for review. The metrics and records shall be kept for three years and
provided to a customer upon request and to Navy Pharmacy Portfolio Program Manager at
NAVMISSA on a quarterly basis and upon request. See the Repairs Definition (Attachment 4)
Attachments for further detail.

The Company shall conduct a customer satisfaction survey on a semi-annual basis and provide an
interactive online tool for customers to provide feedback as needed to measure end user
satisfaction with their service. The results of this survey shall be provided to the Navy Pharmacy
Portfolio Program Manager at NAVMISSA and any other designated Navy personnel they deem
necessary.
        11.3.2. On-Site Support
If, as part of the response to any Call, the “Contractor” determines or user requests that a Field
Service Engineer (FSE) is required to travel to a Customer site to repair or replace Equipment
under Warranty, the “Contractor” shall dispatch a FSE. The “Contractor” shall provide the manner
in which they determine a FSE is required. The dispatching of a FSE for any issue shall be
determined by the “Contractor” but shall meet or exceed the response time provided in Error!
Reference source not found.Error! Reference source not found.. Maintenance and Support
shall also include “Spare Parts” necessary to keep automation functioning Operational Availability
(Ao) as defined in Section 12.3.1 of this guidance, especially for OCONUS sites. The “Contractor”
shall provide FSE support to OCONUS sites by having regional FSE who can respond more quickly
than from the CONUS. For sites that require Country or base clearance the “Contractor” shall be
responsible for all of these access requirements and bear all costs associated with gaining access.
The “Contractor” shall monitor and provide quality assurance reports on the FSE response as part
of the customer support performance reports provided to the Navy Pharmacy Portfolio Program
Manager at NAVMISSA. The “Company shall also provide technical support in accordance with
DoDI 8500.2 and DISA STIGs including the Medical Device STIG in order to keep the automation
operational as required.
        11.3.3. Diagnostic and Repair Services
                                                                                   N62645-11-R-0027

                                                                                        Page 42 of 93

The “Contractor” shall maintain an Operational Availability (Ao) of >99% for all of their installed
hardware or software; Ao = Total Potential Up Time – Total Down Time. If the equipment needs
repair, servicing, or troubleshooting that cannot be performed remotely, the “Contractor” shall
dispatch a FSE. The “Contractor” FSEs shall work inconspicuously alongside pharmacy staff to
ensure products are brought back on line in a timely fashion.
        11.3.4. Preventative maintenance
The “Contractor” shall schedule bi-annual preventive maintenance visits to include scheduled
maintenance, equipment inspections, replacement of defective and worn parts, and testing services
in accordance with the “Company’s” OEM specifications. Operator training shall be provided at no
charge to new staff during bi-annual preventive maintenance visits or performed when deemed
necessary by the site or Navy Pharmacy Portfolio Program Manager at NAVMISSA.
        11.3.5. Parts Replacement
All parts, labor, and travel to perform maintenance service and repairs (preventive or corrective)
shall be included in support fees. Replacement parts shall meet all specifications as the original
part being replaced. All parts shall be installed by the “Contractor”, unless other arrangements are
made with the pharmacy.
        11.3.6. Asset Replacement
If the work to be performed is too complex, or inappropriate to perform on site, the faulty
equipment shall be replaced by “Contractor”, as coordinated with the appropriate local pharmacy
manager. All preparations to necessitate such a move, packing, transportation, and replacement of
the asset shall be performed by “Contractor” at no additional cost to the government.

The “Contractor” shall provide a report to the appropriate local pharmacy manager documenting
the following information on any products replaced at the site:

       Date of removal

       Make, model, serial number, etc

       Reason for removal

       Contract number

       Make, model, and serial number of replacement equipment

All hardware and software support of the system shall provided by The “Contractor” for a fixed,
service charge. Therefore, the “Contractor” shall provide itemized service reports of services
performed or parts replaced after completion of a repair. These reports shall be made available to
the customer.
11.4.   Hardware Software and other Updates
                                                                                   N62645-11-R-0027

                                                                                        Page 43 of 93

“Contractor” shall provide a description of services to provide hardware, software, drug database,
antivirus, and operating system updates. The provision of a configuration management plan shall
be required in accordance with DoD and Navy Information Assurance (IA) policies for any update
schedule to software or other items that can affect an IA posture. The plan shall include the
manner in which the company shall gain approval from the Navy for any update and the manner in
which they shall promulgate the update to each device, verify it has been accomplished and comply
with all Information Assurance Vulnerability Messages (IAVM) as well as communication plan to all
required parties including Information Assurance Officers (IAOs) and Navy Pharmacy Portfolio
Program Manager at NAVMISSA. “Contractor” shall provide the manner in which all system change
requests (SCRs) are collected, managed and coordinated with customers to include validation for
acceptance by both “Contractor” and customer. All SCRs requests shall be communicated to Navy
Pharmacy Portfolio Program Manager at NAVMISSA prior to any deployment to ensure no negative
impact occurs to Navy ATO or other negative impact.
11.5.   Customer Reports
Company’ shall provide a Customer Support Manager who shall communicate regularly in email,
phone or other mechanisms with Pharmacy staff to handle recurring issues facilitate resolutions,
and coordinate system upgrades and ad hoc requests. This Manager shall also serve as a liaison for
customer support for the Navy Pharmacy Portfolio Program Manager at NAVMISSA to enhance
customer support for all sites. The “Contractor” shall maintain a customer portal to provide bi-
directional communication, document storage/retrieval, etc. for both Pharmacy staff and Navy
Pharmacy Portfolio Program Manager at NAVMISSA.
        11.5.1. Call Response Time Report
Call Response Time refers to the time it takes for a call to be answered by a “Contractor” Technical
Support technician. Call response times shall be tracked in real time. Average call response times
for “Contractor” Technical Support shall be reported on a monthly basis to an individual appointed
at time of contract award.
        11.5.2. Call Resolution Time Report
Call Resolution Time is the elapsed calendar time between the time the call is answered and the
time.

       Remote Solution—The call is resolved over the phone or by remote access to the system.

       Field Solution—”Contractor” dispatches a FSE and/or parts.

       OCONUS—Field resolution times outside the continental United States (OCONUS) may vary
        depending on the location of the site.
       11.5.3. System Downtime Monitoring Report
System downtime is the time a system is not able to successfully fill new prescriptions because of
any hardware, software, or procedural issue. Customer shall provide a system downtime
monitoring report when requested by the COR, not more than monthly.

11.6.   Customer Service Portal
The “Contractor” shall maintain a customer portal to provide bi-directional communication,
document storage/retrieval etc. for both the end user and Navy Pharmacy Portfolio Program
Manager at NAVMISSA. The minimum functionality the portal should provide:
                                                                                    N62645-11-R-0027

                                                                                         Page 44 of 93

       Tracking and submission of SCRs as defined in Section 12.4.

       For trouble calls submitted that were resolved by the end user an explanation of the
        problem and the solution.

       The ability to submit service requests for items that are not urgent, but cannot be resolved
        by the end user (e.g. pill image update request).

       Scheduling capability for next onsite maintenance visit and tracking of complete visits.

       Quote requests for non-warranty services.

       Reporting/tracking of system updates as defined in Section 12.4.

       Customer reports as defined in Section 12.5.

       E-mail notification by subscription for updates to the customer portal.
11.7.   Maintain Connectivity
The “Contractor” shall maintain its connection to the B2B gateway or other required DoD
connection as required including all upgrades to their network, facility or personnel to comply with
B2B business rules. The B2B shall be used by the “Contractor” to connect to the System as
necessary to provide support. It is the sole responsibility of the “Contractor” to maintain an
adequate number of personnel who have appropriate Government security clearances to provide
support through the B2B gateway as well as administer all IA related activities including accessing
DoD or Navy network or secure internet locations for compliance related activities or information.
11.8.   Training Programs
“Pharmacy Automation” System training shall be held on site after System Installation using the
production “Pharmacy Automation” system. The “Contractor” shall provide a full detailed
description on customer training. This description should differentiate from new installation
customer training and continual customer training. The timing and manner of this customer
training biannual training shall be described by the “Company.” If the training for users is broken
into distinct categories, the “Contractor” shall describe each category and its purpose.
11.9.   Go-Live Support
“Contractor” Associates shall provide support (technical and training) after the System is turned on
for operation for the time period that “Contractor” is on site providing Go-Live support. During this
time, “Contractor” focuses on (a) reinforcing the key training points explained during training and
(b) working with Customer staff to ease the transition to the new System to ensure all aspects of
the Customer’s workflow are running smoothly.

“Contractor” Associates shall provide a training representative on-site to perform the following
tasks:

       Conduct operations and maintenance training as described above.

       Support the pharmacy staff as the System comes on-line, as described above.
12. TESTING AND VALIDATION REQUIREMENTS
                                                                                    N62645-11-R-0027

                                                                                         Page 45 of 93

A formal validation process shall not be required for the system. A series of informal validation
tests shall be conducted by the contractor to verify that the various functions and features of the
system work as proposed and meet the requirements listed in this document. These tests shall be
witnessed by the PM or their duly authorized representative. The system being provided shall be a
turnkey system including all power, pneumatic, communication, facilities modifications, etc. The
contractor shall be responsible for verifying these systems function properly.


12.1.   Pre-Staged Testing
12.1.1 Initial delivery order-Contractor shall set up the system at a location other than the Navy
Pharmacy to conduct pre-staged testing prior to installation. Contractor shall create a detailed
testing procedure document. The testing procedures in this document shall demonstrate
compliance with the requirements of the base contract as well as that specified in the delivery
order. The testing procedure document shall be subject to government review and approval. Pre-
Staged Testing shall be completed a location to be determined by the “Contractor” and is subject to
government observation and approval prior to installation at the Navy Pharmacy site. The purpose
of this initial set up is to limit downtime of the pharmacy and to ensure a timely installation by
addressing any installation issues which may arise from the custom, site specific configuration of
the system components.

12.1.2. Subsequent delivery orders-Contractor shall set up the system at a location other than the
Navy Pharmacy to ensure the components of the system fit together into the site specific
configuration prior to the installation of each delivery order ordered off of the contract. The
purpose of this initial set up is to limit downtime of the pharmacy and to ensure a timely
installation by addressing any installation issues which may arise from the custom, site specific
configuration of the system components.
12.2.   Site Acceptance Testing
Due to the short time frame that shall be required to install and turn over the system for
production, limited testing shall be conducted after installation and prior to going live. These tests
shall verify proper installation and the interfaces required for the system to operate.
Demonstration of issues that were uncovered but not fully resolved from the factory tests shall be
expected to be demonstrated but this testing may occur during an off-shift period.


13. PROJECT MANAGEMENT REQUIREMENTS
The “Contractor” shall provide the local pharmacy commander a detailed installation schedule
within eight weeks after award of a delivery order. All site preparation requirements shall be
established in advance. This detailed schedule shall include all time required for the installation
for approval by the local commander or their representative prior to being approved. All training
shall be conducted prior to the implementation to enable the personnel to begin immediately using
the system at the completion of installation and testing.
13.1. Project Schedule
                                                                                     N62645-11-R-0027

                                                                                           Page 46 of 93

A project schedule shall be submitted to NAVMISSA, local commander or their designated
representative as part of a delivery order. The schedule shall be revised and re-issued bi-weekly
until the pharmacy begins utilizing the system. A detailed listing of the installation and testing
tasks shall be included in the schedule starting no later than one month before the installation
begins to enable any required local scheduling.

A complete stock location plan shall be prepared for the revised configuration by the selected
vendor and provided to the local commander or their representative for approval. Vendor shall
support pharmacy staff in relocation of medications from existing locations to the new system.
Vendor shall NOT relocate medications independently.
13.2.   Implementation Requirements
A complete turn-key system shall be provided for each delivery order, including all modifications
required to the facility as stated in Section 8.1. This includes removal of current equipment and
installation of all dispensing equipment, printers, counters, shelving, conveyance systems,
computers and software to accomplish a fully functional and readily usable system that meets the
government’s requirements. Prior to implementation, a detailed implementation management
plan shall be provided for approval. Implementation management plan shall include information
required per Section 10.1, Section 10.2 and Section 10.3 including a complete list of equipment
being provided and timeline for implementation including de-installation, construction and
installation. Any physical changes required to the facility to implement the system shall be
included and highlighted as part of this implementation management plan. Any ancillary
equipment required such as air compressors, additional electrical panels or wiring and
communications wiring shall also to be included. This may include removal of current equipment
and as specified in each delivery order.


SECTION G
CONTRACTING OFFICER’S REPRESENTATIVE
For the purpose of this clause, the Contracting Officer’s Representative (COR) is the duly
authorized representative of the Contracting Officer.

The COR shall be appointed by the Contracting Officer and named at time of award.

The COR will perform inspection and acceptance of services to be provided. Inspection and
acceptance will be performed at the locations listed in individual delivery orders.

CONTRACT ADMINISTRATION PLAN

In order to expedite administration of this contract, delineation of duties is provided in the
Contract Administration Plan.


DELIVERY

Delivery dates shall be detailed in individual delivery orders written under contracts awarded as a
result of this solicitation.
                                                                                     N62645-11-R-0027

                                                                                          Page 47 of 93

The Contracting Officer reserves the right to adjust the start date of the contract based on the
actual award date. The ordering period shall not exceed 60 months.

PLACES OF PERFORMANCE

Possible places of performance are stated below and shall be detailed in individual delivery orders
written under contracts awarded as a result of this solicitation.

US Navy Jacksonville Exchange – Jacksonville, FL
US Navy Mayport – Mayport, FL
US Navy Medical Center - San Diego, CA
US Navy Oak Harbor Hosp - Oak Harbor, WA
US Navy Naval Hosp - Portsmouth, VA
US Navy Pharm – Lemoore, CA
US Navy Hosp 00029 - Twentynine Palms, CA
US Navy Makalapa - Pearl Harbor, HI
US Navy Kaneohe Bay - Kaneohe Bay, HI
US Navy Branch Med Clinic - Millington, TN
US Navy Medical Clinic Pharm – Annapolis, MD
US Navy Ambulatory Med Center - Port Hueneme, CA
US Navy Cherry Point Hosp - Cherry Point, NC
US Navy Lejeune Hosp - Camp Lejeune, NC
US Navy Paris Island Pharm - Parris Island, SC
US Navy Quantico - Quantico, VA
US Navy Hospital - Rota, Spain
US Navy Hosp - Agana Heights, Guam
US Navy Hospital - Sigonella, Italy
NHC Newport, Newport, VA
US Navy Sewells Point BMC – Norfolk, VA
BMC Groton- Groton, CT
US Navy Beaufort Hosp - Beaufort, SC
US Navy National Med Center – Bethesda, MD
US Navy Okinawa- Okinawa, Japan

Funding will be provided in individual delivery orders issued under the base contract.




SECTION H

1. DELIVERY ORDER CONTRACT.

1.1. The Government intends to award multiple indefinite delivery indefinite quantity (ID/IQ)
contracts. Requirements will be procured via the award of delivery orders issued against the basic
contracts.

2. DELIVERY ORDER PROCEDURES
                                                                                     N62645-11-R-0027

                                                                                          Page 48 of 93

2.1. Fair Opportunity For Consideration.

2.1.1. One or more delivery orders will be issued during the performance period of the contract.
The Government will provide all awardees a fair opportunity for consideration. In accordance with
FAR 16.505(b), the Contracting Officer will give each awardee a "fair opportunity" to be considered
for each order in excess of $3,000.00 unless one of the conditions in paragraph 2.1.2 below applies.

2.1.2. Exceptions to Fair Opportunity for Consideration. Awardees may not be given a fair
opportunity to be considered for delivery orders which are expected to exceed $3,000.00 when the
Contracting Officer determines one of the following conditions apply:

2.1.2.1. The agency need is of such urgency that providing such an opportunity would result in
unacceptable delays;

2.1.2.2. Only one awardee is capable of providing the supplies or services required at the level of
quality required because the supplies or services ordered are unique or highly specialized;

2.1.2.3. The order should be issued on a sole-source basis in the interest of economy and efficiency
as a logical follow-on to a delivery order already issued under the contract, provided that all
awardees were given fair opportunity to be considered for the original order. For the purposes of
this contract the Contracting Officer may negotiate a sole source logical follow-on delivery order
with the current contractor providing previously competed services for additional work at the
same site. In the event an increase in the amount of previously competed services is required by
the Government, the Contracting Officer may negotiate a sole source logical follow-on delivery
order with the current contractor provided the required additional services/supplies do not
represent more than 20% increase in the original scope of the order. When deciding whether to
negotiate a sole source logical follow-on delivery order with the current contractor, consideration
will be given to the contractor's past performance, continuity of supplies/services, and price.

2.1.2.4. It is necessary to place an order to satisfy a minimum guarantee. All successful contract
awardees are guaranteed a minimum award of a delivery order(s) totaling $25,000.

2.2. The Contracting Officer has broad discretion in determining which awardee should receive a
delivery order. Each delivery order award decision may consider the factors in Section 2.2.
Evaluation factors for each delivery order will be described in the delivery order proposal request.

2.2.1. The price of the delivery order. The proposed price for each delivery order shall include the
required pharmacy system solution inclusive of the system and any required modifications to the
room or space in which the system will be installed. The factors to be considered in evaluating
prices proposed are:

2.2.1.1. Completeness. All price information required by the delivery order proposal request has
been submitted and supplemental price worksheets have been completed.

2.2.1.2. Reasonableness. The degree to which the proposed prices compare to the prices a
reasonable prudent person would expect to incur for the same or similar services.

2.2.2. Technical Factors
2.2.2.1 Design Quality and Capability – The government will evaluate the design, quality and
                                                                                     N62645-11-R-0027

                                                                                          Page 49 of 93

capabilities of the proposed system to determine how well that system improves pharmacy
operations by reducing errors, increasing prescription filling speed/ output, reducing patient wait
times and enhancing inventory management processes. The government will evaluate adherence to
the essential characteristics.

2.2.2.2 Maintainability – The government will evaluate the maintainability of the proposed system
hardware and software.

2.2.3. The past performance of the awardee in previous delivery orders and delivery order
proposals under the contract will be evaluated. Performance within the past 5 years on other
contracts for the facilities covered by the contract may also be considered. This past performance
evaluation will include a review of all aspects of contract performance, both positive and negative,
including but not limited to timeliness of delivery, compliance of the delivered product with the
requirements of the contract but also include continuing support for any product delivered, the
training provided on the product if applicable, and the responsiveness of support and sales
personnel.

2.2.4. Project completion time.

2.2.5. RESERVED

2.2.6. Timeliness of submission of delivery order proposal. Delivery order proposals which are
submitted late may not be considered for award

2.3. When placing orders, the Contracting Officer is not required to prepare formal evaluation
plans, score offers, post notice on the Federal Business Opportunities (FedBizOpps) web site
(unless a Justification for the Exception for Fair Opportunity is approved at the required levels), or
hold discussions or negotiations with each awardee. Even though the Contracting Officer does not
have to comply with the competition rules in Part 6 of the Federal Acquisition Regulation and does
not have to conduct discussions before issuing an order, there will be an internal record of why a
particular offeror provided the best value based on the particular requirements of each delivery
order.

2.4. Issues arising from the placement of orders are not protestable to the Government
Accountability Office unless the protest alleges that the order exceeded the value, scope, or period
of the contract or in the case where a single delivery order exceeds $10 million.

2.5. Delivery Order Proposal Request, Proposal Submission, and delivery order award. The
process for requesting delivery order proposals, evaluating the proposals, selecting an awardee for
each delivery order, issuing the delivery order, and the commencement of services under each
delivery order is shown below.

2.5.1. Delivery Order Proposal Request.

2.5.1.1. The Contracting Officer will issue a written Delivery Order Proposal Request and will
forward it to all awardees unless one of the exceptions to the fair opportunity for consideration
listed above in 2.1 applies.

2.5.1.2. The Delivery Order Proposal Request will include as a minimum the following information:
                                                                                      N62645-11-R-0027

                                                                                           Page 50 of 93


* The due date for proposal submission (generally between 6 to 9 weeks following the date of the
RFP).
* A description of the requirement.
* The place of delivery.
* * Any additional instructions for proposal submission not contained in this section.
* Any other information deemed appropriate by the Contracting Officer.

2.6. Proposal Submission.

2.6.1. If an awardee is unable to submit a proposal, they must notify the Contracting Officer in
writing as soon as practicable. A brief written statement as to why the awardee is unable to submit
a proposal is required. Failure to submit a delivery order proposal without sufficient justification
may be considered as negative past performance information which may jeopardize the award of
future delivery orders.

2.6.2. The contractor's delivery order proposal shall always be required to contain a price section
and may be required to include a past performance or technical section. . Certified cost or pricing
data is not required for individual delivery orders. The proposal shall be forwarded to the Naval
Medical Logistics Command.

2.7. Delivery Order Award.

2.7.1. Upon completion of the evaluation of the past performance, technical and/or price sections,
the Contracting Officer will issue a delivery order to the contractor whose proposal is most
advantageous to the Government considering the evaluation factors stated in the delivery order
proposal request.

2.7.2. In the event issues pertaining to a proposed delivery order cannot be resolved to the
satisfaction of the Contracting Officer, the Contracting Officer reserves the right to withdraw or
cancel the proposed delivery order. In such event, the contractor will be notified, via letter or
email, of the Contracting Officer's decision and this decision shall be final and conclusive and shall
not be subject to the "Disputes" clause or the "Contract Disputes Act".

2.8. Commencement of Performance.

2.8.1. Upon award, a delivery order will be transmitted to the contractor on a DD Form 1155 or
1449.
The required delivery date will be specified in the delivery order.

2.8.2. The Government reserves the right to terminate the contract for cause if the contractor fails
to begin performance.

3. OMBUDSMAN.

3.1. The Ombudsman will review complaints from contractors regarding the award of delivery
orders and ensure that all contractors are afforded a fair opportunity to be considered, consistent
with the procedures in the contract. The delivery order contract Ombudsman for the contract is
the Navy Competition Advocate General. Contractors are encouraged to settle their complaints
                                                                                    N62645-11-R-0027

                                                                                          Page 51 of 93

through the Competition Advocate chain of command, seeking review by the Command
Competition Advocate at the Naval Medical Logistics Command before taking their complaints to
the Navy Competition Advocate General. The Naval Medical Logistics Command's Competition
Advocate can be reached at (301) 619-2157 or at the following address:

Naval Medical Logistics Command
ATTN: Competition Advocate
693 Neiman St.
Fort Detrick, MD 21702-9203

4. PRIOR WRITTEN PERMISSION REQUIRED FOR SUBCONTRACTS.

None of the requirements required by the contract shall be subcontracted to or performed by
persons other than the contractor or the contractor's employees without the prior written consent
of the Contracting Officer.

5. RESTRICTION ON THE USE OF GOVERNMENT-AFFILIATED PERSONNEL.

Except in very limited cases, the federal criminal statutes at 18 USC 203 and 18 USC 205 bar
Government personnel, both active duty and civil service, from working as a contractor employee
in a Government workplace, including a medical treatment facility, either as a second job
("moonlighting") or while on terminal leave. The contractor agrees that, before making an
employment offer to an active duty member or a civil servant, it shall inform the individual of the
potential applicability of these statutes and further agrees to encourage that individual to seek an
advisory opinion from his/her local ethics counsel before accepting an employment offer.

6. RESERVED

7. BACKGROUND INVESTIGATION REQUIREMENTS.

7.1. RESERVED.

7.2 PERSONAL IDENTITY VERIFICATION OF CONTRACTOR PERSONNEL.

7.2.1 The Homeland Security Presidential Directive dated 27 August 2004 requires a mandatory
government-wide standard for secure and reliable forms of identification for Federal employees,
contractors and HCWs who access federally controlled facilities or have access to Federally
controlled IT systems.

7.2.2. Personnel background investigations must be initiated and an advance fingerprint and NAC
results received by the MTF prior to a Common Access Card (CAC) being issued if required.

7.2.3. See Section I, FAR 52.204-9 for additional information.

8. LIABILITY INSURANCE.

8.1. Before commencing work under a contract, the contractor shall certify to the Contracting
Officer in writing that the required insurance has been obtained. The following insurance as
referenced in FAR 28.307 is the minimum insurance required:
                                                                                          N62645-11-R-0027

                                                                                              Page 52 of 93


8.1.1. General liability - Bodily injury liability insurance coverage written on the comprehensive
form of policy of at least $500,000 per occurrence.

8.1.2. Automobile liability - Automobile liability insurance written on the comprehensive form of
policy. The policy shall provide for bodily injury and property damage liability covering the
operation of all automobiles used in connection with performing the contract. Policies covering
automobiles operated in the United States shall provide coverage of at least $200,000 per person
and $500,000 per occurrence for bodily injury and $20,000 per occurrence for property damage.
The amount of liability coverage on other policies shall be commensurate with any legal
requirements of the locality and sufficient to meet normal and customary claims.

8.1.3. Workers' compensation and employer's liability - Contractors are required to comply with
applicable Federal and State workers' compensation and occupational disease statutes. If
occupational diseases are not compensable under those statutes, they shall be covered under the
employer's liability section of the insurance policy, except when contract operations are so
commingled with a contractor's commercial operations that it would not be practical to require
this coverage. Employer's liability coverage of at least $100,000 shall be required, except in States
with exclusive or monopolistic funds that do not permit workers' compensation to be written by
private carriers.




SECTION I
Contract Clauses


CLAUSES INCORPORATED BY REFERENCE


52.203-6           Restrictions On Subcontractor Sales To The Government       SEP 2006
52.204-6           Data Universal Numbering System (DUNS) Number               APR 2008
52.212-3           Offeror Representations and Certification--Commercial Items MAY 2011
52.212-4           Contract Terms and Conditions--Commercial Items             JUN 2010
52.219-10          Incentive Subcontracting Program                            OCT 2001
52.219-16           Liquidated Damages-Subcontracting Plan                     JAN 1999
52.222-4           Contract Work Hours and Safety Standards Act - Overtime JUL 2005
                   Compensation
52.233-2           Service Of Protest                                          SEP 2006
52.237-1           Site Visit                                                  APR 1984
52.247-34          F.O.B. Destination                                          NOV 1991
252.204-7001       Commercial And Government Entity (CAGE) Code Reporting AUG 1999
252.204-7003       Control Of Government Personnel Work Product                APR 1992
252.204-7004 Alt A Central Contractor Registration (52.204-7) Alternate A      SEP 2007
252.204-7007 Alt A Annual Representations and Certifications Alternate A       JAN 2011
252.211-7003       Item Identification and Valuation                           JUN 2011


CLAUSES INCORPORATED BY FULL TEXT
                                                                                                 N62645-11-R-0027

                                                                                                       Page 53 of 93



52.212-5 CONTRACT TERMS AND CONDITIONS REQUIRED TO IMPLEMENT STATUTES OR
EXECUTIVE ORDERS--COMMERCIAL ITEMS (AUG 2011)

(a) The Contractor shall comply with the following Federal Acquisition Regulation (FAR) clauses, which are
incorporated in this contract by reference, to implement provisions of law or Executive orders applicable to
acquisitions of commercial items:

(1) 52.222-50, Combating Trafficking in Persons (FEB 2009) (22 U.S.C. 7104(g)).

___ Alternate I (Aug 2007) of 52.222-50 (22 U.S.C. 7104(g)).

(2) 52.233-3, Protest After Award (AUG 1996) (31 U.S.C. 3553).

(3) 52.233-4, Applicable Law for Breach of Contract Claim (OCT 2004) (Pub. L. 108-77, 108-78).

(b) The Contractor shall comply with the FAR clauses in this paragraph (b) that the Contracting Officer has indicated
as being incorporated in this contract by reference to implement provisions of law or Executive orders applicable to
acquisitions of commercial items: (Contracting Officer check as appropriate.)

 ___ (1) 52.203-6, Restrictions on Subcontractor Sales to the Government (SEP 2006), with Alternate I (OCT 1995)
(41 U.S.C. 253g and 10 U.S.C. 2402).

  ___ (2) 52.203-13, Contractor Code of Business Ethics and Conduct (APR 2010)(Pub. L. 110-252, Title VI,
Chapter 1 (41 U.S.C. 251 note)).

  ___ (3) 52.203-15, Whistleblower Protections under the American Recovery and Reinvestment Act of 2009 (JUN
2010) (Section 1553 of Pub. L. 111-5). (Applies to contracts funded by the American Recovery and Reinvestment
Act of 2009.)

   ___ (4) 52.204-10, Reporting Executive Compensation and First-Tier Subcontract Awards (JUL 2010) (Pub. L.
109-282) (31 U.S.C. 6101 note).

   ___ (5) 52.204-11, American Recovery and Reinvestment Act—Reporting Requirements (JUL 2010) (Pub. L.
111-5).

X ___ (6) 52.209-6, Protecting the Government's Interest When Subcontracting with Contractors Debarred,
Suspended, or Proposed for Debarment (DEC 2010) (31 U.S.C. 6101 note).

  ___ (7) 52.209-10, Prohibition on Contracting with Inverted Domestic Corporations (section 740 of Division C of
Public Law 111-117, section 743 of Division D of Public Law 111-8, and section 745
of Division D of Public Law 110-161).



  ___ (8) 52.219-3, Notice of Total HUBZone Set-Aside or Sole-Source Award (JAN 2011) (15 U.S.C.
657a).
                                                                                                      N62645-11-R-0027

                                                                                                             Page 54 of 93

  ___ (9) 52.219-4, Notice of Price Evaluation Preference for HUBZone Small Business Concerns (JAN 2011) (if
the offeror elects to waive the preference, it shall so indicate in its offer) (15 U.S.C. 657a).

  ___ (10) [Reserved].

  ___ (11)(i) 52.219-6, Notice of Total Small Business Set-Aside (JUNE 2003) (15 U.S.C. 644).

  ___ (ii) Alternate I (OCT 1995) of 52.219-6.

  ___ (iii) Alternate II (MAR 2004) of 52.219-6.

  ___ (12)(i) 52.219-7, Notice of Partial Small Business Set-Aside (JUNE 2003) (15 U.S.C. 644).

  ___ (ii) Alternate I (OCT 1995) of 52.219-7.

  ___ (iii) Alternate II (MAR 2004) of 52.219-7.

  __X_ (13) 52.219-8, Utilization of Small Business Concerns (JAN 2011) (15 U.S.C. 637 (d)(2) and
(3)).

  _X__ (14)(i) 52.219-9, Small Business Subcontracting Plan (JAN 2011) (15 U.S.C. 637(d)(4)).

  ___ (ii) Alternate I (OCT 2001) of 52.219-9

  ___ (iii) Alternate II (OCT 2001) of 52.219-9.

  ___ (iv) Alternate III (JUL 2010) of 52.219-9.

  ___ (15) 52.219-14, Limitations on Subcontracting (DEC 1996) (15 U.S.C. 637(a)(14)).

  ___ (16) 52.219-16, Liquidated Damages--Subcontracting Plan (JAN 1999) (15 U.S.C. 637(d)(4)(F)(i)).

  ___ (17)(i) 52.219-23, Notice of Price Evaluation Adjustment for Small Disadvantaged Business Concerns (OCT
2008) (10 U.S.C. 2323) (if the offeror elects to waive the adjustment, it shall so indicate in its offer).

  ___ (ii) Alternate I (JUNE 2003) of 52.219-23.

  ___ (18) 52.219-25, Small Disadvantaged Business Participation Program--Disadvantaged Status and Reporting
(DEC 2010) (Pub. L. 103-355, section 7102, and 10 U.S.C. 2323).

  ___ (19) 52.219-26, Small Disadvantaged Business Participation Program--Incentive Subcontracting (OCT 2000)
(Pub. L. 103-355, section 7102, and 10 U.S.C. 2323).
                                                                                                  N62645-11-R-0027

                                                                                                        Page 55 of 93


    ___ (20) 52.219-27, Notice of Total Service-Disabled Veteran-Owned Small Business Set-Aside (MAY 2004)
(U.S.C. 657 f).

    ___ (21) 52.219-28, Post Award Small Business Program Rerepresentation (APR 2009) (15 U.S.C.
632(a)(2)).

  ___ (22) 52.219-29 Notice of Total Set-Aside for Economically Disadvantaged Women-Owned Small Business
(EDWOSB) Concerns (APR 2011).

  ___ (23) 52.219-30 Notice of Total Set-Aside for Women-Owned Small Business (WOSB) Concerns Eligible
Under the WOSB Program (APR 2011).

X    ___ (24) 52.222-3, Convict Labor (JUNE 2003) (E.O. 11755).

X    ___ (25) 52.222-19, Child Labor--Cooperation with Authorities and Remedies (JUL 2010) (E.O.
13126).

X    ___ (26) 52.222-21, Prohibition of Segregated Facilities (FEB 1999).

X    ___ (27) 52.222-26, Equal Opportunity (MAR 2007) (E.O. 11246).

X    ___ (28) 52.222-35, Equal Opportunity for Veterans (SEP 2010) (38 U.S.C. 4212).



X    ___ (29) 52.222-36, Affirmative Action for Workers with Disabilities (OCT 2010) (29
U.S.C. 793).

X____ (30) 52.222-37, Employment Reports on Veterans (Sep 2010) (38 U.S.C. 4212).


____ (31) 52.222-40, Notification of Employee Rights Under the National Labor Relations Act (DEC 2010) (E.O.
13496).


___ (32) 52.222-54, Employment Eligibility Verification (JAN 2009). (Executive Order 12989). (Not applicable to
the acquisition of commercially available off-the-shelf items or certain other types of commercial items as prescribed
in 22.1803.)

 ___ (33) (i) 52.223-9, Estimate of Percentage of Recovered Material Content for EPA-Designated Items (MAY
2008) (42 U.S.C. 6962(c)(3)(A)(ii)). (Not applicable to the acquisition of commercially available off-the-shelf
items.)
                                                                                                  N62645-11-R-0027

                                                                                                        Page 56 of 93

    ___ (ii) Alternate I (MAY 2008) of 52.223-9 (42 U.S.C. 6962(i)(2)(c)). (Not applicable to the acquisition of
commercially available off-the-shelf items.)

    ___ (34) 52.223-15, Energy Efficiency in Energy-Consuming Products (DEC 2007) (42 U.S.C. 8259b)

    ___ (35)(i) 52.223-16, IEEE 1680 Standard for the Environmental Assessment of Personal Computer Products
(DEC 2007) (E.O. 13423)              .

    ___ (ii) Alternate I (DEC 2007) of 52.223-16. .

 ___ (36) 52.223-18, Encouraging Contractor Policies to Ban Text Messaging While Driving (AUG 2011).

    ___ (37) 52.225-1, Buy American Act--Supplies (JUNE 2003) (41 U.S.C. 10a-10d).

X ___ (38)(i) 52.225-3, Buy American Act--Free Trade Agreements--Israeli Trade Act (JUN 2009) (41 U.S.C.
10a-10d, 19 U.S.C. 3301 note, 19 U.S.C. 2112 note, 19 U.S.C. 3805 note, Pub. L. 108-77, 108-78, 108-286, 108-
302, 109-53, 109-169, 109-283, and 110-138).

    ___ (ii) Alternate I (JAN 2004) of 52.225-3.

    ___ (iii) Alternate II (JAN 2004) of 52.225-3.

    ___ (39) 52.225-5, Trade Agreements (AUG 2009) (19 U.S.C. 2501, et seq., 19 U.S.C. 3301 note).

    ___ (40) 52.225-13, Restrictions on Certain Foreign Purchases (JUN 2008) (E.O.'s, proclamations, and statutes
administered by the Office of Foreign Assets Control of the Department of the Treasury).

    ___ (41) 52.226-4, Notice of Disaster or Emergency Area Set-Aside (Nov 2007) (42 U.S.C. 5150).

    ___ (42) 52.226-5, Restrictions on Subcontracting Outside Disaster or Emergency Area (Nov 2007) (42 U.S.C.
5150).

    ___ (43) 52.232-29, Terms for Financing of Purchases of Commercial Items (FEB 2002) (41 U.S.C. 255(f), 10
U.S.C. 2307(f))

    ___ (44) 52.232-30, Installment Payments for Commercial Items (OCT 1995) (41 U.S.C. 255(f), 10 U.S.C.
2307(f)).

X    ___ (45) 52.232-33, Payment by Electronic Funds Transfer--Central Contractor Registration (OCT 2003) (31
U.S.C. 3332).
                                                                                                    N62645-11-R-0027

                                                                                                          Page 57 of 93

  ___ (46) 52.232-34, Payment by Electronic Funds Transfer--Other than Central Contractor Registration (MAY
1999) (31 U.S.C. 3332)

  ___ (47) 52.232-36, Payment by Third Party (FEB 2010) (31 U.S.C. 3332).

  ___ (48) 52.239-1, Privacy or Security Safeguards (AUG 1996) (5 U.S.C. 552a).

  ___ (49)(i) 52.247-64, Preference for Privately Owned U.S.-Flag Commercial Vessels (FEB 2006) (46 U.S.C.
Appx 1241(b) and 10 U.S.C. 2631).

  ___ (ii) Alternate I (APR 2003) of 52.247-64.

  ____

(c) The Contractor shall comply with the FAR clauses in this paragraph (c), applicable to commercial services, that
the Contracting Officer has indicated as being incorporated in this contract by reference to implement provisions of
law or Executive orders applicable to acquisitions of commercial items: (Contracting Officer check as appropriate.)

  ____ (1) 52.222-41, Service Contract Act of 1965 (Nov 2007) (41 U.S.C. 351, et seq.).

  ____ (2) 52.222-42, Statement of Equivalent Rates for Federal Hires (MAY 1989) (29 U.S.C. 206 and 41 U.S.C.
351, et seq.).

  ____ (3) 52.222-43, Fair Labor Standards Act and Service Contract Act--Price Adjustment (Multiple Year and
Option Contracts) (SEP 2009) (29 U.S.C. 206 and 41 U.S.C. 351, et seq.).

  ____ (4) 52.222-44, Fair Labor Standards Act and Service Contract Act--Price Adjustment (SEP 2009) (29 U.S.C.
206 and 41 U.S.C. 351, et seq.)

  ____ (5) 52.222-51, Exemption from Application of the Service Contract Act to Contracts for Maintenance,
Calibration, or Repair of Certain Equipment--Requirements (Nov 2007) (41 U.S.C. 351, et seq.).

  ____ (6) 52.222-53, Exemption from Application of the Service Contract Act to Contracts for Certain Services--
Requirements (FEB 2009) (41 U.S.C. 351, et seq.).

  ____ (7) 52.226-6, Promoting Excess Food Donation to Nonprofit Organizations (Mar           2009) (Pub. L. 110-247).



  ____ (8) 52.237-11, Accepting and Dispensing of $1 Coin (SEP 2008)(31 U.S.C. 5112(p)(1)).

(d) Comptroller General Examination of Record. The Contractor shall comply with the provisions of this paragraph
(d) if this contract was awarded using other than sealed bid, is in excess of the simplified acquisition threshold, and
does not contain the clause at 52.215-2, Audit and Records--Negotiation.
                                                                                                    N62645-11-R-0027

                                                                                                           Page 58 of 93


(1) The Comptroller General of the United States, or an authorized representative of the Comptroller General, shall
have access to and right to examine any of the Contractor's directly pertinent records involving transactions related to
this contract.

(2) The Contractor shall make available at its offices at all reasonable times the records, materials, and other
evidence for examination, audit, or reproduction, until 3 years after final payment under this contract or for any
shorter period specified in FAR Subpart 4.7, Contractor Records Retention, of the other clauses of this contract. If
this contract is completely or partially terminated, the records relating to the work terminated shall be made available
for 3 years after any resulting final termination settlement. Records relating to appeals under the disputes clause or to
litigation or the settlement of claims arising under or relating to this contract shall be made available until such
appeals, litigation, or claims are finally resolved.

(3) As used in this clause, records include books, documents, accounting procedures and practices, and other data,
regardless of type and regardless of form. This does not require the Contractor to create or maintain any record that
the Contractor does not maintain in the ordinary course of business or pursuant to a provision of law.

(e) (1) Notwithstanding the requirements of the clauses in paragraphs (a), (b), (c), and (d) of this clause, the
Contractor is not required to flow down any FAR clause, other than those in this paragraph (e)(1)in a subcontract for
commercial items. Unless otherwise indicated below, the extent of the flow down shall be as required by the
clause—

(i) 52.203-13, Contractor Code of Business Ethics and Conduct (APR 2010) (Pub. L. 110-252, Title VI, Chapter 1
(41 U.S.C. 251 note).

(ii) 52.219-8, Utilization of Small Business Concerns (DEC 2010) (15 U.S.C. 637(d)(2) and (3)), in all subcontracts
that offer further subcontracting opportunities. If the subcontract (except subcontracts to small business concerns)
exceeds $650,000 ($1.5 million for construction of any public facility), the subcontractor must include 52.219-8 in
lower tier subcontracts that offer subcontracting opportunities.

(iii) Reserved.

(iv) 52.222-26, Equal Opportunity (MAR 2007) (E.O. 11246).

(v) 52.222-35, Equal Opportunity for Veterans (SEP 2010) (38 U.S.C. 4212).

(vi) 52.222-36, Affirmative Action for Workers with Disabilities (OCT 1998) (29 U.S.C. 793).

(vii) 52.222-40, Notification of Employee Rights Under the National Labor Relations Act (DEC 2010) (E.O. 13496).
Flow down required in accordance with paragraph (f) of FAR clause 52.222-40.

(viii) 52.222-41, Service Contract Act of 1965 (Nov 2007) (41 U.S.C. 351, et seq.).

(ix) 52.222-50, Combating Trafficking in Persons (FEB 2009) (22 U.S.C. 7104(g)).

Alternate I (AUG 2007) of 52.222-50 (22 U.S.C. 7104(g)).

(x) 52.222-51, Exemption from Application of the Service Contract Act to Contracts for Maintenance, Calibration,
or Repair of Certain Equipment--Requirements (Nov 2007) (41 U.S.C. 351, et seq.).

(xi) 52.222-53, Exemption from Application of the Service Contract Act to Contracts for Certain Services--
Requirements (FEB 2009) (41 U.S.C. 351, et seq.).

(xii) 52.222-54, Employment Eligibility Verification (JAN 2009).
                                                                                                      N62645-11-R-0027

                                                                                                            Page 59 of 93


(xiii) 52.226-6, Promoting Excess Food Donation to Nonprofit Organizations. (MAR 2009) (Pub. L. 110-247). Flow
down required in accordance with paragraph (e) of FAR clause 52.226-6.

(xiv) 52.247-64, Preference for Privately Owned U.S.-Flag Commercial Vessels (FEB 2006) (46 U.S.C. Appx
1241(b) and 10 U.S.C. 2631). Flow down required in accordance with paragraph (d) of FAR clause 52.247-64.

(2) While not required, the contractor May include in its subcontracts for commercial items a minimal number of
additional clauses necessary to satisfy its contractual obligations.

(End of clause)




52.216-18     ORDERING. (OCT 1995)

(a) Any supplies and services to be furnished under this contract shall be ordered by issuance of delivery orders or
task orders by the individuals or activities designated in the Schedule. Such orders may be issued from contract
award date through 60 months from contract award date.

(b) All delivery orders or task orders are subject to the terms and conditions of this contract. In the event of conflict
between a delivery order or task order and this contract, the contract shall control.

(c) If mailed, a delivery order or task order is considered "issued" when the Government deposits the order in the
mail. Orders may be issued orally, by facsimile, or by electronic commerce methods only if authorized in the
Schedule.

(End of clause)



52.252-1    SOLICITATION PROVISIONS INCORPORATED BY REFERENCE (FEB 1998)

This solicitation incorporates one or more solicitation provisions by reference, with the same force and effect as if
they were given in full text. Upon request, the Contracting Officer will make their full text available. The offeror is
cautioned that the listed provisions may include blocks that must be completed by the offeror and submitted with its
quotation or offer. In lieu of submitting the full text of those provisions, the offeror may identify the provision by
paragraph identifier and provide the appropriate information with its quotation or offer. Also, the full text of a
solicitation provision may be accessed electronically at this/these address(es):

http://www.farsite.hil.af.mil


(End of provision



252.212-7001 CONTRACT TERMS AND CONDITIONS REQUIRED TO IMPLEMENT STATUTES OR
EXECUTIVE ORDERS APPLICABLE TO DEFENSE ACQUISITIONS OF COMMERCIAL ITEMS (JUN 2011)
                                                                                                  N62645-11-R-0027

                                                                                                        Page 60 of 93

(a) The Contractor agrees to comply with the following Federal Acquisition Regulation (FAR) clause which, if
checked, is included in this contract by reference to implement a provision of law applicable to acquisitions of
commercial items or components.

 ___ 52.203-3, Gratuities (APR 1984) (10 U.S.C. 2207).

(b) The Contractor agrees to comply with any clause that is checked on the following list of Defense FAR
Supplement clauses which, if checked, is included in this contract by reference to implement provisions of law or
Executive orders applicable to acquisitions of commercial items or components.

 (1) ___252.203-7000, Requirements Relating to Compensation of Former DoD Officials (JAN 2009) (Section 847
of Pub. L. 110-181).

 (2) ___ 252.203-7003, Agency Office of the Inspector General (SEP 2010) (Section 6101 of Pub. L. 110-252, 41
U.S.C. 3509 note).

 (3) ___ 252.205-7000, Provision of Information to Cooperative Agreement Holders (DEC 1991) (10 U.S.C.
2416).

 (4) ___ 252.219-7003, Small Business Subcontracting Plan (DoD Contracts) (OCT 2010) (15 U.S.C. 637).

 (5) ___ 252.219-7004, Small Business Subcontracting Plan (Test Program) (JAN 2011) (15 U.S.C. 637 note).

  (6)(i) ___ 252.225-7001, Buy American Act and Balance of Payments Program (JAN 2009) (41 U.S.C. 10a-10d,
E.O. 10582).

(ii) ____ Alternate I (DEC 2010) of 252.225-7001.

 (7) ____ 252.225-7008, Restriction on Acquisition of Specialty Metals (JUL 2009) (10 U.S.C. 2533b).

 (8) ____ 252.225-7009, Restriction on Acquisition of Certain Articles Containing Specialty Metals (JAN 2011) (10
U.S.C. 2533b).

 (9) ____ 252.225-7012, Preference for Certain Domestic Commodities (JUN 2010) (10 U.S.C. 2533a).

 (10) ____ 252.225-7015, Restriction on Acquisition of Hand or Measuring Tools (JUN 2005) (10 U.S.C.
2533a).

 (11) ____ 252.225-7016, Restriction on Acquisition of Ball and Roller Bearings (JUN 2011) (Section 8065 of
Public Law 107-117 and the same restriction in subsequent DoD appropriations acts).

 (12) )(i) ___ 252.225-7021, Trade Agreements (JUN 2011) (19 U.S.C. 2501-2518 and 19 U.S.C. 3301 note).

 (ii) ___ Alternate I (SEP 2008)

 (iii) ___ Alternate II (DEC 2010) of 252.225-7021.

 (13) ____ 252.225-7027, Restriction on Contingent Fees for Foreign Military Sales (APR 2003) (22 U.S.C.
2779).

 (14) ____ 252.225-7028, Exclusionary Policies and Practices of Foreign Governments (APR 2003) (22 U.S.C.
2755).
                                                                                               N62645-11-R-0027

                                                                                                     Page 61 of 93

 (15)(i) ____ 252.225-7036, Buy American Act--Free Trade Agreements--Balance of Payments Program (DEC
2010) (41 U.S.C. 10a-10d and 19 U.S.C. 3301 note).

 (ii) ___ Alternate I (JUL 2009) of 252.225-7036.

(iii) ___ Alternate II (DEC 2010) of 252.225-7036.

 (iv) ___ Alternate III (DEC 2010) of 252.225-7036.

 (16) ____ 252.225-7038, Restriction on Acquisition of Air Circuit Breakers (JUN 2005) (10 U.S.C.
2534(a)(3)).

 (17) ____ 252.226-7001, Utilization of Indian Organizations, Indian-Owned Economic Enterprises, and Native
Hawaiian Small Business Concerns (SEP 2004) (Section 8021 of Public Law 107-248 and similar sections in
subsequent DoD appropriations acts).

 (18) ____ 252.227-7015, Technical Data--Commercial Items (MAR 2011) (10 U.S.C. 2320).

 (19) ____ 252.227-7037, Validation of Restrictive Markings on Technical Data (SEP 1999) (10 U.S.C. 2321).

X (20) ____ 252.232-7003, Electronic Submission of Payment Requests and Receiving Reports (MAR 2008) (10
U.S.C. 2227).

(21) ____252.237-7010, Prohibition on Interrogation of Detainees by Contractor Personnel (NOV 2010) (Section
1038 of Pub. L. 111-84).

X(22) ____ 252.237-7019, Training for Contractor Personnel Interacting with Detainees (SEP 2006) (Section 1092
of Public Law 108-375).

 (23) ____ 252.243-7002, Requests for Equitable Adjustment (MAR 1998) (10 U.S.C. 2410).

  (24)____252.246-7004, Safety of Facilities, Infrastructure, and Equipment for Military Operations (OCT 2010)
(Section 807 of Public Law 111-84).

 (25)____ 252.247-7003, Pass-Through of Motor Carrier Fuel Surcharge Adjustment to the Cost Bearer (SEP 2010)
(Section 884 of Public Law 110-417).

X (26)(i) ____ 252.247-7023, Transportation of Supplies by Sea (MAY 2002) (10 U.S.C. 2631).

 (ii) ____ Alternate I (MAR 2000) of 252.247-7023.

 (iii) ____ Alternate II (MAR 2000) of 252.247-7023.

 (iv) ____ Alternate III (MAY 2002) of 252.247-7023.

X (27) ____ 252.247-7024, Notification of Transportation of Supplies by Sea (MAR 2000) (10 U.S.C. 2631).

(c) In addition to the clauses listed in paragraph (e) of the Contract Terms and Conditions Required to Implement
Statutes or Executive Orders--Commercial Items clause of this contract (FAR 52.212-5), the Contractor shall include
the terms of the following clauses, if applicable, in subcontracts for commercial items or commercial components,
awarded at any tier under this contract:

(1) 252.237-7010, Prohibition on Interrogation of Detainees by Contractor Personnel (NOV 2010) (Section 1038 of
Pub. L. 111-84).
                                                                                                   N62645-11-R-0027

                                                                                                         Page 62 of 93


(2) 252.237-7019, Training for Contractor Personnel Interacting with Detainees (SEP 2006) (Section 1092 of Public
Law 108-375).

(3) 252.247-7003, Pass-Through of Motor Carrier Fuel Surcharge Adjustment to the Cost Bearer (SEP 2010)
(Section 884 of Public Law 110-417).

(4) 252.247-7023, Transportation of Supplies by Sea (MAY 2002) (10 U.S.C. 2631).

(5) 252.247-7024, Notification of Transportation of Supplies by Sea (MAR 2000) (10 U.S.C. 2631).

(End of clause)



SECTION J
List of Attachments

ATTACHMENT 1: CONTRACT ADMINISTRATION PLAN (CAP)

ATTACHMENT 2: NOTIONAL SOLUTION

ATTACHMENT 3: INFORMATION ASSURANCE

ATTACHMENT 4: REPAIR DEFINITIONS

ATTACHMENT 5: TABLE OF DELIVERABLES

ATTACHMENT 6: PRICING CONFIGURATIONS

ATTACHMENT 7: MDS2 FORM

ATTACHMENT 8: NOTIONAL SOLUTION DIAGRAMS


SECTION K
ORCA Certification Sheet

Online Representations and Certifications Application (ORCA)

I certify that all of the representations and certifications completed in ORCA are current, complete and accurate as of
the date of my signature provided on the SF1449, Solicitation Offer and Award for RFP # N62645-11-R-0027.




_________________________________                      __________
Signature                                                  Date

_________________________________
Title

_________________________________
Organization
                                                                                                   N62645-11-R-0027

                                                                                                         Page 63 of 93


_________________________________
E-Mail Address

_________________________________
Phone




OR


I certify that all of the representations and certifications completed in ORCA are current, complete and accurate as of
the date of my signature provided on the SF 1449, Solicitation ,Contract, Order for Commercial Items RFP #
N62645-11-R-0027 with the exception of the following:

(list any changes)



_________________________________                      __________
Signature                                                  Date

_________________________________
Title

_________________________________
Organization

_________________________________
E-Mail Address

_________________________________
Phone




SECTION L

INSTRUCTIONS TO OFFERORS
L.1. SUBMISSION OF COST OR PRICING DATA.

L.1.1. It is expected that this contract will be awarded based upon a determination that there is
adequate price competition; therefore, the offeror is not required to submit additional cost or price
data (beyond that required by Section L.2) or to certify cost or pricing data with its proposal.

L.1.2. If, after receipt of the proposals, the Contracting Officer determines that adequate price
competition does not exist in accordance with FAR 15.403-3 and 15.403-4, the offeror shall provide
other information requested to be submitted to determine fairness and reasonableness of price, or
other than certified cost or pricing data as requested by the Contracting Officer.
                                                                                      N62645-11-R-0027

                                                                                           Page 64 of 93


L.2. PROPOSAL CONTENT AND INSTRUCTIONS FOR PREPARATION OF PROPOSALS.

L.2.1. Introduction and Purpose - This section specifies the format and content that offerors shall
use in this Request for Proposal (RFP). The intent is not to restrict the offerors in the manner in
which they will perform their work but rather to ensure a certain degree of uniformity in the
format of the responses for evaluation purposes. Offerors must submit a proposal that is legible
and comprehensive enough to provide the basis for a sound evaluation by the Government.
Information provided should be precise, factual, and complete. Legibility, clarity, completeness,
and responsiveness are of the utmost importance. Proposals shall be in the form prescribed by,
and shall contain a response to, each of the areas identified in Section L.2. Any proposal which does
not provide, as a minimum, that which is required in this solicitation may be determined to be
substantially incomplete and not warrant any further consideration.

L.2.1.1. The proposal shall be submitted in four separate volumes:

        Volume I – Past Performance Component
        Volume II – Technical Approach (a.)Compliance with General Functional Systems
        Requirement Document b.) Design Quality and Capability c.) Maintainability)
        Volume III – Price (Reasonableness and Completeness)
        Volume IV – Small Business Subcontracting/Participation Plan

A complete Volume I, Past Performance component, Volume II, Technical component, Volume III,
Price component and Volume IV, Small Business Plan shall be submitted by the closing date
specified in Section A of this solicitation. If any one proposal volume is received past the stated
closing date specified in this solicitation, the entire proposal will be considered late. No further
consideration will be given to any offeror who submits any of these volumes late IAW FAR
15.208(b).

L.2.2. Volume I: Past Performance Component. In accordance with file submission requirements
given in this section, the offeror shall submit the following:

L.2.2.1. The offeror shall describe its past performance on up to five (5) similar contracts it has held
within the last three (3) years that are for the same or similar equipment to that which is detailed
in this solicitation or affirmatively state the offeror possesses no relevant past performance
directly related to or similar past performance. Offerors who present similar contracts shall
provide a detailed explanation demonstrating the relevance of the contracts to the requirements of
the solicitation. Offerors shall demonstrate (1) the functional performance of the proposed or
similar pharmacy automation systems that the offeror has delivered to previous customers, and (2)
the quality and timeliness of the technical assistance, hardware and software updates/upgrades
that the vendor has supplied to its customers following the initial fielding of those systems.

The Government reserves the right to contact any references.

L.2.2.2. The offeror shall provide the following information regarding its past performance:

L.2.2.2.1 Contract number(s), award date and dates of performance.
                                                                                      N62645-11-R-0027

                                                                                           Page 65 of 93

L.2.2.2.2 Name, phone number, and e-mail address of a point of contact at the federal, state, local
government or commercial entity for which the contract was performed. Contractor shall verify the
validity of the contact information provided.

L.2.2.2.3 Dollar value of the contract.

L.2.2.2.4 Description of the equipment provided under the contract.

L.2.2.2.5 The number, type and severity of any quality or delivery problems in performing the
contract, the corrective action taken and the effectiveness of the corrective action (if applicable).

L.2.2.2.6 Any other relevant information.

L.2.2.2.7 Answer “Has the POC agreed to be to be contacted as a reference?”

L.2.2.4. The government reserves the right to consider other past performance information at its
disposal, in addition to any information obtained from the references provided above. The
government is likely to randomly select references provided for contact and does not commit to
contact every reference.

L.2.3. Volume II: Technical Approach (Compliance with the Functional Systems Requirement
Document; Design Quality and Capability; Maintainability) are of equal importance). In
accordance with file submission requirements given in this section, the offeror shall submit the
following:

PART A: Written Proposal Narrative- The written narrative shall include the requirement listed in
L.2.3.1 Adherence to GFSR, L.2.3.2 Design Quality and Capability and L.2.3.3 Maintainability.

L.2.3.1. Compliance with GFSR: Offerors shall provide sufficient written technical documentation
(including, but not limited to: Project engineering and design, final design review, product
literature, specifications, features, pertinent maintenance or operator manuals, and warranty
information) to allow for thorough evaluation of proposal.

L.2.3.2.Design Quality and Capability – The offeror shall demonstrate the design, quality and
capabilities of the proposed system to determine how well that system improves pharmacy
operations by reducing errors, increasing prescription filling speed/ output, reducing patient wait
times and enhancing inventory management processes

L.2.3.3. Maintainability – The vendor shall demonstrate the maintainability of the proposed system
hardware and software. The vendor shall included a completed Manufacturers' Security
Disclosure Statement (MDS2) form which is Attachment 7, The vendor’s current status in the
certification and accreditation process (C&A; i.e.DIACAP process for system (or components)
and involvement with the DIACAP process shall be addressed, as well as any industry standard
or best practice (i.e. International Organization for Standardization, Underwriters Laboratory,
etc.), in the vendor’s proposal.

PART B- Verbal Presentation- Each offeror will be required to do a verbal presentation in
accordance with L.2.3.1.2.
                                                                                     N62645-11-R-0027

                                                                                          Page 66 of 93


L.2.3.1.2. – Each offeror will be required to do a verbal presentation of their technical proposal
including a demonstration on the use and capabilities of the proposed system software which the
pharmacy staff would interface with during system operations. Verbal presentations shall be
scheduled approximately two weeks of solicitation closing at Fort Detrick in Frederick, Maryland.
Verbal presentations shall be no more than 2 hours. Verbal presentations will be evaluated in
conjunction with the written technical approach proposal.

L.2.4. Volume III: Price. See Pricing Configuration Attachment for assistance in pricing proposals.
In accordance with file submission requirements given in this section, the offeror shall submit the
following:

L.2.4.1. Standard Form 1449. Completed in accordance with L.2.5.4.1.

L.2.4.2. Amendments. Completed in accordance with L.2.5.4.2.

L.2.4.3. Completed Section A.

L.2.4.4. Completed Section B (Required CLINS)

L.2.4.5. CCR. The offeror shall be registered and current in CCR IAW FAR 52.204-7.

L.2.5 Volume IV: Small Business Contracting and Participation Plan

All offerors are required to submit a small business participation plan. If applicable (for large
business concern offerors under the assigned NAICS code herein), the offeror shall submit a
subcontracting plan in accordance with FAR Clause 52.219-9 and DFARS Clause 252.219-7003 (for
reference see FAR 19.704 and DFARS 219-704). The negotiation of a subcontracting plan shall not
be considered discussions or a reopening of Solicitation N62645-11-R-0019. The subcontracting
plan requirement is not applicable to small business concerns qualified as such under the NAICS
code assigned to this solicitation. Master subcontracting plans can be included as an appendix to
the subcontracting plan and will not count towards the page count. Offerors shall include the name
of any proposed subcontractors and any applicable references.

L.2.6. FILE SUBMISSION. Only electronic files will be accepted unless otherwise noted in the
subsections of this paragraph.

L.2.6.1 The Past Performance component, Technical Approach component, Price component and
Small Business Subcontracting and Participation Plan shall be submitted in electronic format as
files on CD-ROMs to the address specified in Section A. Files shall be in Microsoft Office for
Windows format (2007), either .doc, .docx, .xls or .xlsx files as specified herein. Consent letters may
be submitted as a .pdf file and included in the Past Performance submission.

L.2.6.2 Three identical sets of CD-ROMs shall be submitted. Each CD-ROM shall be labeled as to the
name of the offeror and the contents of the CD-ROM.

L.2.6.3. Past Performance component (Volume I) and Technical component (Volume II).
                                                                                      N62645-11-R-0027

                                                                                            Page 67 of 93

L.2.6.3.1. The Past Performance files shall be submitted on a Past Performance component CD-ROM
and the CD-ROM files shall be named: [name of offeror] Past Performance component.docx. The
Technical Approach files shall be submitted on a Technical Approach component CD-ROM and the
CD-ROM files shall be named: [name of offeror] Technical Approach component.docx. The Small
Business Subcontracting and Participation Plan files shall be submitted on a Small Business
component CD-ROM and the CD-ROM files shall be named: [name of offeror] Small Business
component.docx.

L.2.6.3.2. RESERVED

L.2.6.3.3. Each component (Volume I, II, IV) file shall be in a Microsoft Word for Windows (2007)
file (.docx) with 1 inch margins all around, Times New Roman font of not less than 10 point font
size. Each page of each document shall have a footer indicating the name of the offeror and “page X
of Y.”

L.2.6.3.4. The total number of the pages submitted for Volume I (Past Performance) SHALL NOT
EXCEED 5 PAGES, excluding a cover letter and consent letters. If Volume I contains more than 5
pages, only the first 5 pages will be evaluated. The total number of the pages submitted for Volume
II (Technical) SHALL NOT EXCEED 50 PAGES, excluding a cover letter. If Volume II contains more
than 50 pages, only the first 50 pages will be evaluated. Small Business Participation Plan has no
page limit.

L.2.6.4. Price component (Volume III). The Price component CD-ROM shall include all of the
following items:

L.2.6.4.1. Standard Form (SF) 1449. This form will be provided to the offeror electronically as part
of the solicitation package. It shall be appropriately completed, inclusive of the offeror's name,
address, and required Commercial and Government Entity (CAGE) codes, and signed. The offeror's
identity will be determined by the name submitted on the SF 1449. It is not necessary to submit
the entire solicitation.

L.2.6.4.2. Amendments. Each amendment shall be acknowledged through instructions in Block 11
of the SF 30. Signed copies of the cover page are acceptable. It is not necessary to submit the entire
amendment.

L.2.6.4.3. Section A. Offeror’s Information Form of Section A shall be completed. The offeror must
fill in every field on the form for it to be considered complete. (Please note that failure to submit a
completed form may result in rejection of the offeror's entire proposal.)

L.2.6.5. The offeror is responsible for ensuring that submitted CD-ROMs include all complete files
and are not physically damaged nor contain corrupted files such that they are not readable by the
Government. The offeror shall ensure that the three sets of CD-ROMs are identical.

L.2.6.6. Completed ORCA certification and verification of current CCR registration.

L.3. PROPOSAL EVALUATION.

L.3.1. The Technical Approach factor (comprised of three subfactors: Compliance with the
Functional Systems Requirement Document, Design Quality and Capability, and Maintainability) is
                                                                                    N62645-11-R-0027

                                                                                         Page 68 of 93

significantly more important than the Past Performance, Small Business Participation Plan, and
Price. The combination of the Technical Approach factor, Past Performance and Small Business
Participation is significantly more important than the combined Price component evaluation
factors (Completeness and Reasonableness). Price may be the determining factor if two or more
proposals are substantially equivalent in terms of technical, past performance and small business
participation.

L.3.1.1. Information in one volume will not be considered for the purposes of another volume, (i.e.,
Past Performance information in the Technical component that fails to address the same
information in Past Performance component).

L.3.2. The Government reserves the right to award without discussions. It should be noted that
award may be made to other than the lowest priced offer. Offerors are cautioned that each initial
offer shall contain the offeror's best terms.

L.3.3. Contract awards will be based on evaluation of Technical Approach, Past Performance, Price
and small business participation components. All Delivery Orders will be awarded via a Delivery
Order Proposal Request after contract award, within the guidelines stated in Section H. All
successful contract awardees will receive, at a minimum, a Delivery Order award for $25,000
during the life of the contracts.

L.3.4. Volume I. Past Performance Component.

L.3.4.1. Past Performance Component Evaluation. Past Performance components submitted in
response to this solicitation will be evaluated in accordance with the following:

L.3.4.1.1. The Government will first evaluate the offeror's Past Performance information to
determine whether the company has relevant Past Performance.

L.3.4.1.2. The Government will evaluate past performance on up to five (5) similar contracts it has
held within the last three (3) years that are for the same or similar equipment to that which is
detailed in this solicitation or affirmatively state the offeror possesses no relevant past
performance directly related to or similar past performance. The Government will then evaluate
(1) the functional performance of the proposed or similar pharmacy automation systems that the
offeror has delivered to previous customers, and (2) the quality and timeliness of the technical
assistance, hardware and software updates/upgrades that the vendor has supplied to its customers
following the initial fielding of those systems.

L.3.4.1.3. The Government is not restricted from evaluating and considering other relevant Past
Performance information in its possession and may contact references for that information
including references not provided by the offeror.

L.3.4.1.4. Based on the relevance, quality, and quantity of the offeror’s Past Performance, the
Government will assess the risk to the Government of future non-performance of solicitation
requirements by the offeror. The Government will not assume that the offeror possesses any Past
Performance unless it is specified in the Past Performance component.

L.3.5. Volume II. Technical Approach.
                                                                                   N62645-11-R-0027

                                                                                        Page 69 of 93

L.3.5.1. Technical Approach. The Technical Approach submitted in response to this solicitation will
be evaluated in accordance with the following:

L.3.5.1.1. Compliance with GFSR - The Government will evaluate the contractor’s adherence to the
GFSR.

L.3.5.1.2 Design Quality and Capability – The government will evaluate the design quality and
capabilities of the proposed system to determine how well that system improves pharmacy
operations by reducing errors, increasing prescription filling speed/ output, reducing patient wait
times and enhancing inventory management processes.

L.3.5.1.3. Maintainability – The government will evaluate the maintainability of the proposed
system hardware and software.

L.3.5.2 The government will evaluate the verbal presentation in conjunction with the written
proposal to evaluate the technical approach above. The Government will not assume that the
offeror possesses any capability or knowledge unless it is specified in the Technical component.

L.3.6. Volume III. Price Component.

L.3.6.1. Price Component Evaluation. Adequate price competition is expected for this acquisition.
See Pricing Configuration Attachment for assistance in pricing. The Price component will be
evaluated with consideration to the following factors:

L.3.6.1.1. COMPLETENESS.
The offeror's Price component will be examined to ensure that the following have been completed:
Standard Form 1449 has been completed; all amendments have been acknowledged; the offeror is
registered in ORCA IAW FAR 52.204-8 and DFARS 252.204-7007 and submitted the ORCA
Certification Sheet; the offeror is registered in CCR IAW FAR 52.204-7, and Section A’s Offeror’s
Information form is completed.

L.3.6.1.2. REASONABLENESS. The offeror’s Price component will be examined to determine the
degree to which the proposed prices compare to the prices a reasonable prudent person would
expect to incur for the same or similar systems. Since awards will be made on a best value basis,
the Contracting Officer reserves the right to award a premium providing the total prices are
determined to be reasonable.

L.3.7 Volume IV. Small Business Participation Plan and Subcontracting Plan

All offerors are required to submit a small business participation plan. If applicable (for large
business concern offerors under the assigned NAICS code herein), the offeror shall submit a
subcontracting plan in accordance with FAR Clause 52.219-9 and DFARS Clause 252.219-7003 (for
reference see FAR 19.704 and DFARS 219-704). The negotiation of a subcontracting plan shall not
be considered discussions or a reopening of Solicitation N62645-11-R-0027. The subcontracting
plan requirement is not applicable to small business concerns qualified as such under the NAICS
code assigned to this solicitation. Master subcontracting plans can be included as an appendix to
the subcontracting plan and will not count towards the page count. Offerors shall include
subcontractor names and applicable references.
                                                                                      N62645-11-R-0027

                                                                                           Page 70 of 93


L.4. QUESTIONS. Offerors must submit all questions concerning this solicitation in writing to the
Contract Specialist listed below. NAVMEDLOGCOM must receive the questions no later than 10
calendar days after the issue date (Block 5 of SF1449) of this solicitation. The Contract Specialist
will answer questions that may affect offers in an amendment to the solicitation. The Contract
Specialist will not disclose the source of the questions. Questions shall be referred to:

Naval Medical Logistics Command
ATTN: Code 02, Courtney Piar
693 Neiman Street
Fort Detrick, MD 21702
Email:courtney.piar@med..navy.mil.

If you send your question via e-mail and do not receive acknowledgment of receipt by
NAVMEDLOGCOM within 72 hours, you are requested to resend your question.


L.5.3. The reviewing authority for the Contracting Officer is the Director of Acquisition
Management, NAVMEDLOGCOM, Code 02, 693 Neiman Street, Fort Detrick, MD 21702-9203.
Agency procurement protests should clearly identify the initial adjudicating official, i.e., the,
“Contracting Officer” or the, “Reviewing Official”.

L.5.4. Offerors should note this review of the Contracting Officer’s decision will not extend GAO’s
timeliness requirements. Therefore, any subsequent protest to GAO must be filed within 10 days of
knowledge of initial adverse agency action.

L.5.5. ORCA- Section K - Representations, Certifications and Other Statements of Offerors of this
Solicitation. The offeror shall complete the annual representations and certifications electronically
through the Online Representations and Certifications Application (ORCA) at http://orca.bpn.gov.
The offeror shall verify their ORCA is current, accurate, complete and applicable to this solicitation
as of the date of this offer and are incorporated in this offer by reference, except for any applicable
changes identified in Section K, FAR Clause 52.204-8 and DFARS 252.204-7007. The applicable
NAICS code for this solicitation is 423450. In addition to submission to ORCA the offeror shall
complete the ORCA Certification Sheet.




SECTION M
Evaluation Factors

The Technical evaluation factor is significantly more important than the Past Performance, Small
Business Participation Plan and Price. The combination of the Technical evaluation factor, Past
Performance and Small Business Participation is significantly more important than the combined
Price component evaluation factors (Completeness and Reasonableness).
                                                                                    N62645-11-R-0027

                                                                                         Page 71 of 93


TECHNICAL APPROACH: (SubFactors are of Equal Importance)
a. Compliance with Requirements Document- The Government will evaluate the contractor’s
proposal for adherence to the GFSR.
b. Design Quality and Capability – The government will evaluate the design quality and capabilities
of the proposed system to determine how well that system improves pharmacy operations by
reducing errors, increasing prescription filling speed/ output, reducing patient wait times and
enhancing inventory management processes.
c. Maintainability – The government will evaluate the maintainability of the proposed system
hardware and software.

The government will evaluate the verbal presentation in conjunction with the written proposal to
evaluate the technical approach above.

2. PAST PERFORMANCE:

The Government will evaluate the offeror's Past Performance information to determine whether
the company has relevant Past Performance. In doing so the Government will examine the offeror’s
past performance on up to five (5) similar contracts it has held within the last three (3) years that
are for the same or similar equipment to that which is detailed in this solicitation or affirmatively
state the offeror possesses no relevant past performance directly related to or similar past
performance. The Government will then evaluate (1) the functional performance of the proposed
or similar pharmacy automation systems that the offeror has delivered to previous customers, and
(2) the quality and timeliness of the technical assistance, hardware and software
updates/upgrades that the vendor has supplied to its customers following the initial fielding of
those systems. Both factors listed above are of equal importance in determining a past
performance rating. The government reserves the right to consider other past performance
information at its disposal, in addition to any information obtained from the references provided
above. The government is likely to randomly select references provided for contact and does not
commit to contact every reference.

3. SMALL BUSINESS PARTICIPATION PLAN: All offerors (both large and small businesses) will be
evaluated on the level of small business commitment that they are demonstrating for the proposed
acquisition, and their level of commitment to utilizing small businesses in performance of prior
contracts. The small business participation plan factor will be evaluated on an “Acceptable (Pass)”
or “Unacceptable (Fail)” basis and one of these ratings will be assigned accordingly. The small
business plan will be evaluated on the following: (1) The extent to which such firms are specifically
identified in proposals; (2) The extent of commitment to use such firms (for example, enforceable
commitments are to be weighted more heavily than non-enforceable ones); (3) The complexity and
variety of the work small firms are to perform. An acceptable rating will consist of 5% or more small
business participation.
4.PRICE: The offeror will be evaluated for reasonableness and completeness.
a.Reasonableness - The offeror’s Price component will be evaluated separately to determine the
degree to which the proposed prices compare to the prices a reasonable prudent person would
expect to incur for the same or similar equipment. Since awards will be made on a best value basis,
the Contracting Officer reserves the right to award a premium providing the prices are determined
to be reasonable.
                                                                                                   N62645-11-R-0027

                                                                                                         Page 72 of 93

b. Completeness- The offeror's Price proposal will be examined to ensure that the following have
been completed: Standard Form 26 has been completed; all amendments have been acknowledged;
the offeror is registered in ORCA IAW FAR 52.204-8 and DFARS 252.204-7007 and submitted the
ORCA Certification Sheet (located in Section J) ; the offeror is registered in CCR IAW FAR 52.204-7
and Section A’s Offeror’s Information form is completed.
Each factor shall be submitted separately from all other factors.




RATING SCALES
Technical evaluations shall utilize the ratings listed in Table 1.

Table 1. Combined Technical/Risk Ratings
Color               Rating                       Description
Blue                Outstanding                  Proposal meets requirements and indicates an exceptional approach
                                                 and understanding of the requirements. Strengths far outweigh any
                                                 weaknesses. Risk of unsuccessful performance is very low.
Purple                 Good                      Proposal meets requirements and indicates a thorough approach and
                                                 understanding of the requirements. Proposal contains strengths which
                                                 outweigh any weaknesses. Risk of unsuccessful performance is low.
Green                  Acceptable                Proposal meets requirements and indicates an adequate approach and
                                                 understanding of the requirements. Strengths and weaknesses are
                                                 offsetting or will have little or no impact on contract performance.
                                                 Risk of unsuccessful performance is no worse than moderate.
Yellow                 Marginal                  Proposal does not clearly meet requirements and has not demonstrated
                                                 an adequate approach and understanding of the requirements. The
                                                 proposal has one or more weaknesses which are not offset by
                                                 strengths. Risk of unsuccessful performance is high.
Red                    Unacceptable              Proposal does not meet requirements and contains one or more
                                                 deficiencies. Proposal is unawardable.


                                Rating Standards for Small Business Participation Plan

Raing                                                                   Definition
Acceptable (Pass)                         Offeror’s level of small business commitment in current proposal or
                                          utilization of small businesses in performance of prior contracts is
                                          meaningful.
Unacceptable (Fail)                       Offeror’s level of small business commitment in current proposal or
                                          utilization of small businesses in performance of prior contracts is
                                          not meaningful.

*To Receive an acceptable rating, an offeror must include small business participation percentage of at least 5%.

Past Performance Confidence Assessment Ratings
Each offeror will be assigned a Confidence Assessment Rating. There are two aspects to the past performance
evaluation. The first is to evaluate the offeror’s past performance to determine how relevant a recent effort
                                                                                                  N62645-11-R-0027

                                                                                                        Page 73 of 93

accomplished by the offeror is to the effort to be acquired through the source selection. Aspects of relevancy include
similarity of service/support, complexity, dollar value, contract type, and degree of subcontract/teaming. The
following describes the Past Performance Relevancy Rating.

Past Performance Relevancy Rating
Rating                     Definition
Very Relevant              Present/past performance effort involved essentially the same scope and
                           magnitude of effort and complexities this solicitation requires.
Relevant                   Present/past performance effort involved similar scope and magnitude of
                           effort and complexities this solicitation requires.
Somewhat Relevant          Present/past performance effort involved some of the scope and magnitude of
                           effort and complexities this solicitation requires.
Not Relevant               Present/past performance effort involved little or none of the scope and
                           magnitude of effort and complexities this solicitation requires.

The past performance evaluation results in an assessment of the offeror’s probability of meeting the solicitation
requirements The past performance evaluation considers each offeror's demonstrated recent and relevant record of
performance in supplying products and services that meet the contract’s requirements. One performance confidence
assessment rating is assigned for each offeror after evaluating the offeror's recent past performance, focusing on
performance that is relevant to the contract requirements. See FAR 15.305.

Performance Confidence Assessment Rating
Rating                 Description
Substantial Confidence Based on the offeror’s recent/relevant performance record, the Government has a
                       high expectation that the offeror will successfully perform the required effort.
Satisfactory           Based on the offeror’s recent/relevant performance record, the Government has a
Confidence             reasonable expectation that the offeror will successfully perform the required
                       effort.
Limited Confidence     Based on the offeror’s recent/relevant performance record, the Government has a
                       low expectation that the offeror will successfully perform the required effort.
No Confidence          Based on the offeror’s recent/relevant performance record, the Government has
                       no expectation that the offeror will be able to successfully perform the required
                       effort.
Unknown Confidence     No recent/relevant performance record is available or the offeror’s performance
(Neutral)              record is so sparse that no meaningful confidence assessment rating can be
                       reasonably assigned.



CONTRACT ADMINISTRATION PLAN
                                                 ATTACHMENT 1

                                  CONTRACT ADMINISTRATION PLAN (CAP)


In order to expedite the administration of this contract, the following delineation of duties is provided. The names,
addresses and phone numbers for these offices or individuals are included elsewhere in the contract award document.
The office or individual designated as having responsibility should be contacted for any questions, clarifications, or
information regarding the administration function assigned.

1. The Procuring Contract Office (PCO) is responsible for:
        a. All pre-award duties such as solicitation, negotiation and award of contracts.
        b. Any information or questions during the pre-award stage of the procurement.
                                                                                                    N62645-11-R-0027

                                                                                                          Page 74 of 93

         c.   Freedom of Information inquiries.
         d.   Changes in contract terms and/or conditions.
         e.   Post award conference.

2. The Contract Administration Office (CAO) is responsible for matters specified in the FAR 42.302 and DFARS
42.302 except those areas otherwise designated as the responsibility of the Contracting Officer's Representative
(COR) or someone else herein.

3. The paying office is responsible for making payment of proper invoices after acceptance is documented.

4. The Contracting Officer's Representative (COR) is responsible for interface with the contractor and performance
of duties such as those set forth below. It is emphasized that only the PCO/CAO has the authority to modify the
terms of the contract. In no event will any understanding, agreement, modification, change order, or other matter
deviating from the terms of the basic contract between the contractor and any other person be effective or binding on
the Government. If in the opinion of the contractor an effort outside the scope of the contract is requested, the
contractor shall promptly notify the PCO in writing. No action may be taken by the contractor unless the PCO or
CAO has issued a contractual change. The COR duties are as follows:

         a.   Technical Interface
              (1) The COR is responsible for all Government technical interface concerning the contractor and
              furnishing technical instructions to the contractor. These instructions may include: technical
              advice/recommendations/clarifications of specific details relating to technical aspects of contract
              requirements; milestones to be met within the general terms of the contract or specific subtasks of the
              contract; or, any other interface of a technical nature necessary for the contractor to perform the work
              specified in the contract. The COR is the point of contact through whom the contractor can relay
              questions and problems of a technical nature to the PCO.

              (2) The COR is prohibited from issuing any instruction which would constitute a contractual change.
              The COR shall not instruct the contractor how to perform. If there is any doubt whether technical
              instructions contemplated fall within the scope of work, contact the PCO for guidance before
              transmitting the instructions to the contractor.

         b.   Contract Surveillance
              (1) The COR shall monitor the contractor's performance and progress under the contract. In
              performing contract surveillance duties, the COR should exercise extreme care to ensure that he/she
              does not cross the line of personal services. The COR must be able to distinguish between surveillance
              (which is proper and necessary) and supervision (which is not permitted). Surveillance becomes
              supervision when you go beyond enforcing the terms of the contract. If the contractor is directed to
              perform the contract services in a specific manner, the line is being crossed. In such a situation, the
              COR's actions would be equivalent to using the contractor's personnel as if they were government
              employees and would constitute transforming the contract into one for personal services.

              (2) The COR shall monitor contractor performance to see that inefficient or wasteful methods are not
              being used. If such practices are observed, the COR is responsible for taking reasonable and timely
              action to alert the contractor and the PCO to the situation.

              (3) The COR will take timely action to alert the PCO to any potential performance problems. If
              performance schedule slippage is detected, the COR should determine the factors causing the delay and
              report them to the PCO, along with the contractor's proposed actions to eliminate or overcome these
              factors and recover the slippage. Once a recovery plan has been put in place, the COR is responsible
              for monitoring the recovery and keeping the PCO advised of progress.

              (4) If the Contractor Performance Assessment Reporting System (CPARS) is applicable to the contract
              you are responsible for completing a Contractor Performance Assessment Report (CPAR) in the
                                                                                            N62645-11-R-0027

                                                                                                  Page 75 of 93

     CPARS Automated Information System (AIS). The initial CPAR, under an eligible contract, must
     reflect evaluation of at least 180 days of contractor performance. The completed CPAR, including
     contractor comments if any, (NOTE: contractors are allowed 30 days to input their comments) should
     be available in the CPARS AIS for reviewing official (PCO) review no later than 270 days after start of
     contract performance. Subsequent CPARs covering any contract option periods should be ready at 1-
     year intervals thereafter.

c.   Invoice Review and Approval/Inspection and Acceptance

     (1) The COR is responsible for quality assurance of services performed and acceptance of the services
     or deliverables. The COR shall expeditiously review copies of the contractor's invoices or vouchers,
     certificate of performance and all other supporting documentation to determine the reasonableness of
     the billing. In making this determination, the COR must take into consideration all documentary
     information available and any information developed from personal observations.

     (2) The COR must indicate either complete or partial concurrence with the contractor's invoice/voucher
     by executing the applicable certificate of performance furnished by the contractor. The COR must be
     cognizant of the invoicing procedures and prompt payment due dates detailed elsewhere in the contract.

     (3) The COR will provide the PCO and the CAO with copies of acceptance documents such as
     Certificates of Performance.

     (4) The COR shall work with the Contractor to obtain and execute a final invoice no more than 60 days
     after completion of contract performance. The COR shall ensure that the invoice is clearly marked as a
     “Final Invoice.”

d.   Contract Modifications. The COR is responsible for developing the statement of work for change
     orders or modifications and for preparing an independent government cost estimate of the effort
     described in the proposed statement of work.

e.   Administrative Duties

     (1) The COR shall take appropriate action on technical correspondence pertaining to the contract and
     for maintaining files on each contract. This includes all modifications, government cost estimates,
     contractor invoices/vouchers, certificates of performance, DD 250 forms and contractor's status reports.

     (2) The COR shall maintain files on all correspondence relating to contractor performance, whether
     satisfactory or unsatisfactory, and on trip reports for all government personnel visiting the contractor's
     place of business for the purpose of discussing the contract.

     (3) The COR must take prompt action to provide the PCO with any contractor or technical code request
     for change, deviation or waiver, along with any supporting analysis or other required documentation.

f.   Government Furnished Property. When government property is to be furnished to the contractor, the
     COR will take the necessary steps to insure that it is furnished in a timely fashion and in proper
     condition for use. The COR will maintain adequate records to ensure that property furnished is returned
     and/or that material has been consumed in the performance of work.

g.   Security. The COR is responsible for ensuring that any applicable security requirements are strictly
     adhered to.

h.   Standards of Conduct. The COR is responsible for reading and complying with all applicable agency
     standards of conduct and conflict of interest instructions.
                                                                                                   N62645-11-R-0027

                                                                                                         Page 76 of 93

         i.   Written Report/Contract Completion Statement.

              (1) The COR is responsible for timely preparation and submission to the PCO, of a written, annual
              evaluation of the contractors performance. The report shall be submitted within 30 days prior to the
              exercise of any contract option and 60 days after contract completion. The report shall include a
              written statement that services were received in accordance with the Contract terms and that the
              contract is now available for close-out. The report shall also include a statement as to the use made of
              any deliverables furnished by the contractor.

              (2) If the Contractor Performance Assessment Reporting System (CPARS) is applicable to the contract
              you are responsible for completing a final Contractor Performance Assessment Report (CPAR) in the
              CPARS with 30 days of contract completion.

              (3) The COR is responsible for providing necessary assistance to the Contracting Officer in performing
              Contract Close-out in accordance with FAR 4.804, Closeout of Contract Files.

5. The Technical Assistant (TA), if appointed, is responsible for providing routine administration and monitoring
assistance to the COR. The TA does not have the authority to provide any technical direction or clarification to the
contract. Duties that may be performed by the TA are as follows:

         a.   Identify contractor deficiencies to the COR.

         b.   Review contract deliverables, recommend acceptance/rejection, and provide the COR with
              documentation to support the recommendation.

         c.   Assist in preparing the final report on contractor performance for the applicable contract in accordance
              with the format and procedures prescribed by the COR.

         d.   Identify contract noncompliance with reporting requirements to the COR.

         e.   Review contractor status and progress reports, identify deficiencies to the COR, and provide the COR
              with recommendations regarding acceptance, rejection, and/or Government technical clarification
              requests.

         f.   Review invoices and provide the COR with recommendations to facilitate COR certification of the
              invoice.

         g.   Provide the COR with timely input regarding technical clarifications for the statement of work, possible
              technical direction to provide the contractor, and recommend corrective actions.

         h.   Provide detailed written reports of any trip, meeting, or conversation to the COR subsequent to any
              interface between the TA and contractor.




NOTIONAL SOLUTION
                                                 ATTACHMENT 2
                                                                                    N62645-11-R-0027

                                                                                         Page 77 of 93


NOTIONAL PROCESS DESIGN APPROACH – EXTERNAL ATTACHMENT


INFORMATION ASSURANCE
                                         ATTACHMENT 3

                                      Information Assurance
Naval Medical Logistics Command (NMLC) will determine whether proposals meet Navy
Information Assurance (IA) requirements to include the Department of Defense Information
Assurance Certification and Accreditation Process (DIACAP), Public Key Infrastructure (PKI) and
Common Access Card (CAC) authentication compliance. The DIACAP artifacts required prior to
installation include the System Identification Profile (SIP), DIACAP Implementation Plan (DIP), Plan
of Actions and Milestones (POA&M) and Risk Analysis. These documents shall be delivered to
NMLC, Code 03, Imaging Informatics Division for review and processing.

Navy Platform IT (PIT) Designation

 All DON information systems as defined in Department of Defense Directive (DoDD) 8500.1 shall
be certified and accredited (C&A) for operation. The C&A process, (DIACAP) is applicable to all
DON-owned or controlled information systems that receive, process, store, display or transmit
Department of Defense (DoD) information, regardless of Mission Assurance Category (MAC)
classification or sensitivity, except, per DoDD 8500.1 Paragraph 2.3; IT that is considered PIT.
Certain medical technologies may be designated as PIT by the Navy Operational Designated
Accrediting Authority (ODAA); however the PIT designation itself does not constitute an Approval
to Operate (ATO). The PIT system will require a PIT ATO. The DIACAP SIP, DIP, POA&M and Risk
Analysis documents are required in order to obtain a PIT ATO. In addition to these documents,
vendors will be required to scan the PIT system for vulnerabilities prior to connection to the DON
network.

            According to DoDD 8500.1, Paragraph E2.1.16.4; PIT refers to computer resources,
           both hardware and software, that are physically part of, dedicated to, or essential in
           real time to the mission performance of special-purpose systems. Medical technologies,
           and specifically medical imaging and monitoring systems are considered special-
           purpose mission technologies according to this definition.

            The PIT designation issued by the ODAA may be used by the Program Manager (PM)
           to obtain a PIT ATO in order to prove compliance with C&A requirements, but is
           cautioned that the appropriate IA controls must still be built into the IT to comply with
           acquisition requirements. The contractor shall work with Navy Program Managers to
           ensure their systems meet these requirements.

            The Contractor will be required to propose an acceptable approach to selecting IA
           controls starting from the baseline set on DoD Instruction 8500.2 B, commensurate
           with the system’s Mission Assurance Category (MAC) and Confidentiality Level.

            The Contractor shall support Navy IA representatives in creation of the PIT
           designation request packages to include all relevant configuration, software and IA
                                                                                   N62645-11-R-0027

                                                                                        Page 78 of 93

           data. The following documents will assist in creating the PIT designation request
           package;
                       Digital Imaging and Communications in Medicine (DICOM) Conformance
                          Statement (if applicable)
                       Food and Drug Administration (FDA) Certification (510k)
                       Integrating the Healthcare Enterprise (IHE) Integration Statement
                       International Organization for Standardization (ISO) Statement (if
                          applicable)
                       Manufacturer Disclosure Statement for Medical Device Security (MDS2)


DIACAP

For those systems that do not meet the requirements for designation as PIT, the contractor shall
comply with DIACAP requirements as specified by the DoD that meet appropriate DoD and Navy IA
requirements. The contractor shall initiate the process by providing the required documentation
necessary to receive an ATO. The contractor shall make their device or system delivered against
this contract, available for Security Test and Evaluation (ST&E) and initiate the process well in
advance of a contract delivery order. The requirements shall be met before the contractor's system
is authorized to access DoD data or interconnect with any DoD network that receives, processes,
stores, displays or transmits DoD data. An ATO, at a minimum, will be required before a device or
system is installed. The contractor shall ensure the proper contractor support staff is available to
participate in all phases of the DIACAP process. They include but are not limited to;

            Completing and maintaining all documentation necessary to obtain an ATO.

            Attending and supporting DIACAP and C&A meetings with Navy IA representatives.

            Supporting/conducting the vulnerability mitigation process to comply with IA
           controls listed in DoD Instruction 8500.2.

            Supporting the C&A Team during system security testing.

            Contractors must confirm that their systems are locked down prior to initiating C&A
           testing.


Navy Business to Business (B2B) Gateway

 All contractor systems that will communicate with Department of the Navy (DON) systems will
interconnect through the established Military Health System (MHS) Business to Business (B2B)
gateway. For all Web applications, contractors will connect to the DISA-established Web DMZ.

            Contractors will connect to the B2B gateway via a contractor procured Internet
           Service Provider (ISP) connection and assume all responsibilities for establishing and
           maintaining their connectivity to the B2B gateway. This will include acquiring and
           maintaining the circuit to the B2B gateway and acquiring a FIPS-140-2 Virtual Private
           Network (VPN)/Firewall device compatible with the MHS VPN device. Maintenance
                                                                                   N62645-11-R-0027

                                                                                        Page 79 of 93

            and repair of contractor procured VPN equipment shall be the responsibility of the
            contractor.

             Contractors shall configure their network to support access to government systems
            (e.g., configure ports and protocols for access).

             Contractors shall provide full time connections to a TIER1 or TIER2 ISP. Dial-up ISP
            connections are not acceptable.

             Contractors will comply with DoD guidance regarding allowable ports, protocols and
            risk mitigation strategies

       Prior to accessing DON networks, all contractors will be required to complete a DISA Form
       2875 System Authorization Access Request form (SAAR) and submit it to NMLC, Code 03,
       Imaging Informatics Division for processing. The contractor will be required to complete
       applicable DoD IA training.


Ports Protocols and Services

Vendors shall follow all current DoD and Defense Information Systems Agency (DISA) standards
and requirements for acceptable Ports, Protocols, and Services. Any requests for exception to using
the current DISA Ports, Protocols, and Services standards requires an request for exception sent
through the Program Manager to the DAA.

IPv6

The proposed system shall be Internet Protocol version 6 (IPv6) capable or the vendor must
provide a detailed project, migration or planning documentation to show when the proposed
system shall be IPv6 capable.

Minimum IPv6 capabilities include:

           Conformant with the IPv6 standards profile contained in the DoD IT Standards Registry
            (DISR);
           Maintaining interoperability in heterogeneous environments with IPv4;
           Commitment to upgrade as the IPv6 standard evolves;
           Availability of vendor IPv6 technical support.

The vendor must be able to demonstrate or provide documentation to prove that their product is
IPv6 capable. IPv6 'capable' is defined as having the capability of receiving, processing and
forwarding IPv6 packets and/or interfacing with other IPv6 capable systems/devices and in a
manner similar to IPv4. In order to demonstrate IPv6 compliance, the vendor should submit the
following documentation:

           Provide a diagram showing IPv6 core configuration, to include IPv6 addressing, internal
            network connectivity and topology, external network connectivity, and IPv6 traffic flow;
           Submit a list of core components to include vendor/manufacturer IPv6 compliance;
                                                                                     N62645-11-R-0027

                                                                                           Page 80 of 93

          Submit a report that illustrates testing of IPv6 compliance, to include test scripting, logs
           and results.

Manuals

The vendor shall provide two paper copies or an electronic copy, with the right to duplicate in
support of the system to be installed at the requesting site, of both the operator and service
manuals. The service manual shall be equal to or greater in detail than the service manuals
provided to vendor’s own service technicians.

Personnel Security and User Access Control

Because of the unique circumstances presented by DoD and DON networks, personnel security
requirements shall be followed to ensure appropriate precautions are taken prior to allowing
vendor personnel access to the network. Any vendor personnel that will be accessing the medical
device/system while installed on the hospital network will be required to have a National Agency
Check (NAC) completed. Typically, this requires an investigation to support a “Public Trust
Position” and requires the person(s) to complete and submit a Standard Form 85P (SF85P),
Questionnaire for Public Trust Positions, via the Electronic Personnel Security Questionnaire
(EPSQ). Questions relating to SF85Ps and the EPSQ process may be directed to 1-888-282-7682 or
online at http://www.dss.mil/index.htm. Contractor personnel accessing equipment connected to
the hospital network will be required to complete a System Authorization Access Request-Navy
(SAAR-N) (form OPNAV 5239/14). Copies of this form can be obtained from the Navy PACS Office.
Additionally, contractor personnel are required to complete the annual DoD IA training
requirements.

The Commander, Joint Task Force-Global Network Operations (JTF-GNO) has mandated the
implementation of Public Key Infrastructure (PKI) across the DoD on all unclassified servers.
These servers must be configured to only trust DoD authorized Certificate Authorities. PK-enabled
systems may be configured to accept External Certificate Authorities (ECA), but only in cases where
the Information Assurance Manager (IAM) has coordinated with the Bureau of Medicine and
Surgery (BUMED) Chief Information Officer (CIO). The trusting of ECA certificates and associated
access control techniques must be documented. This requirement is applicable to medical devices
that are installed on DoD networks. Vendors must indicate their willingness and ability to meet
this requirement. The DoD has also mandated two factor authentication for access to information
systems. This is most commonly accomplished by using a DoD issued Common Access Card (CAC).

Access to the medical devices will be limited to authorized users as determined by local policy.
Vendors whose systems do not yet meet the requirement for CAC authentication must indicate
their willingness to do so, and offer a timeline for compliance.

Complete administrative system rights shall be provided to the government System Administrator
for the purpose of conducting device vulnerability scans as needed.


Information Assurance Vulnerability Management (IAVM) Program

The IAVM Program is focused on maintaining a secure platform as new vulnerabilities and exploits
are discovered and released through various software developers and security agencies. The core
                                                                                   N62645-11-R-0027

                                                                                        Page 81 of 93

requirements of a successful IAVM Program include a documented process for the testing,
implementation and reporting of mitigations for Information Assurance Vulnerability Alerts
(IAVAs), Information Assurance Vulnerability Bulletins (IAVBs)) and Computer Tasking Orders
(CTO) . The DoD releases IAVAs and IAVBs for local action on the various platforms across the
enterprise network. Each Navy Military Treatment Facility (MTF) is responsible for managing their
local network. Most DoD IAVAs/IAVBs originate from a real world event such as a patch release or
vulnerability notification from a software vendor (e.g. Windows or Oracle patch release), or an
alert released from the US Cyber Command (USCYBERCOM). CTOs vary greatly from an IAVA/B in
that they are typically not a simple patch but instead a systematic change in the DoD's IA Security
Posture (e.g. Host Based Security System (HBSS), Information Operations Condition (INFOCON) 3,
PKI Phase 2, etc.) and often require configuration changes (e.g. CAC authentication) or loading of
additional software (e.g. HBSS).To have an effective IAVM Program, vendors must be proactive in
monitoring emerging threats. Some recommended sources for IAVM Program support are:

      General Vulnerability alerts and tasking, all platforms:
       https://www.cybercom.mil/J3/IAVM/default.aspx
      Navy Cyber Defense Operations Command (NCDOC): https://www.ncdoc.navy.mil/
      Navy Online Compliance Reporting System: https://www.iava.navy.mil/

To support the IAVM Program, the contractor shall provide a primary and secondary point of
contact for compliance actions. The point of contact shall provide, upon receipt of a vulnerability
message, an acknowledgement of that receipt. The vendor shall thoroughly test all mitigations for
the vulnerability, and upon applying the mitigation to the system, report compliance. Receipt and
compliance messages shall occur within the stipulated time window, as stated in the vulnerability
message or other official notification.

Contractors are required to meet these requirements and shall have a documented process to
demonstrate organizational security throughout the medical system/device lifecycle. The
processes shall clearly demonstrate security’s role in the product development phase, and the
processes the vendor employs to react to vulnerabilities, validate required patches, communicate
status and required actions to their customers, and the follow up service support to address patch
implementation.

The contractor shall acknowledge that in order to ensure compliance with security requirements,
medical systems/devices will be subject to automated security scans and penetration tests. If the
contractor feels that these scans will adversely affect system performance or become potentially
unsafe for use on patients, they must state so in writing. Contractors shall also provide other
documentation supporting their claim.

Business Associate Agreement

In accordance with DoD 6025.18-R “Department of Defense Health Information Privacy
Regulation” the Contractor meets the definition of Business Associate. Therefore, a Business
Associate Agreement is required to comply with both the Health Insurance Portability and
Accountability Act (HIPAA) Privacy and Security regulations. This clause serves as that agreement
whereby the Contractor agrees to abide by all applicable HIPAA Privacy and Security requirements
regarding health information as defined in this clause, and DoD 6025.18-R and DoD 8580.02-R, as
amended. Additional requirements will be addressed when implemented.
                                                                                      N62645-11-R-0027

                                                                                           Page 82 of 93

       (a) Definitions. As used in this clause generally refer to the Code of Federal Regulations
(CFR) definition unless a more specific provision exists in DODI 6025.18-R.

       Individual has the same meaning as the term ``individual'' in 45 CFR 164.501 and 164.103
and shall include a person who qualifies as a personal representative in accordance with 45 CFR
164.502(g).

       Privacy Rule means the Standards for Privacy of Individually Identifiable Health
Information at 45 CFR part 160 and part 164, subparts A and E.

       Protected Health Information has the same meaning as the term ``protected health
information'' in 45 CFR 164.501, limited to the information created or received by The Contractor
from or on behalf of The Government.

       Electronic Protected Health Information has the same meaning as the term “electronic
protected health information” in 45 CFR 160.103.

       Required by Law has the same meaning as the term ``required by law'' in 45 CFR 164.501
and 164.103.

       Secretary means the Secretary of the Department of Health and Human Services or his/her
designee.

       Security Rule means the Health Insurance Reform: Security Standards at 45 CFR part 160,
162 and part 164, subpart C.

   Terms used, but not otherwise defined, in this Clause shall have the same meaning as those
terms in 45 CFR 160.103, 164.501 and 164.304.

        (b) The Contractor shall not use or further disclose Protected Health Information other
than as permitted or required by the Contract or as Required by Law.

       (c) The Contractor shall use appropriate safeguards to prevent use or disclosure of the
Protected Health Information other than as provided for by this Contract.

        (d) The Contractor shall use administrative, physical, and technical safeguards that
reasonably and appropriately protect the confidentiality, integrity, and availability of the electronic
protected health information that it creates, receives, maintains, or transmits in the execution of
this Contract.

        (e) The Contractor shall mitigate, to the extent practicable, any harmful effect that is known
to the Contractor of a use or disclosure of Protected Health Information by the Contractor in
violation of the requirements of this Contract.

        (f) The Contractor shall report to the Government any security incident involving protected
health information of which it becomes aware.

        (g) The Contractor shall report to the Government any use or disclosure of the Protected
Health Information not provided for by this Contract of which the Contractor becomes aware of.
                                                                                   N62645-11-R-0027

                                                                                         Page 83 of 93


        (h) The Contractor shall ensure that any agent, including a subcontractor, to whom it
provides Protected Health Information received from, or created or received by the Contractor on
behalf of the Government, agrees to the same restrictions and conditions that apply through this
Contract to the Contractor with respect to such information.

       (i) The Contractor shall ensure that any agent, including a subcontractor, to whom it
provides electronic Protected Health Information, agrees to implement reasonable and appropriate
safeguards to protect it.

         (j) The Contractor shall provide access, at the request of the Government, and in the time
and manner designated by the Government to Protected Health Information in a Designated Record
Set, to the Government or, as directed by the Government, to an Individual in order to meet the
requirements under 45 CFR 164.524.

       (k) The Contractor shall make any amendment(s) to Protected Health Information in a
Designated Record Set that the Government directs or agrees to pursuant to 45 CFR 164.526 at the
request of the Government or an Individual, and in the time and manner designated by the
Government.

        (l) The Contractor shall make internal practices, books, and records relating to the use and
disclosure of Protected Health Information received from, or created or received by the Contractor
on behalf of, the Government, available to the Government, or at the request of the Government to
the Secretary, in a time and manner designated by the Government or the Secretary, for purposes
of the Secretary determining the Government’s compliance with the Privacy Rule.

       (m) The Contractor shall document such disclosures of Protected Health Information and
information related to such disclosures as would be required for the Government to respond to a
request by an Individual for an accounting of disclosures of Protected Health Information in
accordance with 45 CFR 164.528.

        (n) The Contractor shall provide to the Government or an Individual, in time and manner
designated by the Government, information collected in accordance with this Clause of the
Contract, to permit the Government to respond to a request by an Individual for an accounting of
disclosures of Protected Health Information in accordance with 45 CFR 164.528.

General Use and Disclosure Provisions

    Except as otherwise limited in this Clause, the Contractor may use or disclose Protected Health
Information on behalf of, or to provide services to, the Government for treatment, payment, or
healthcare operations purposes, in accordance with the specific use and disclosure provisions
below, if such use or disclosure of Protected Health Information would not violate the Privacy Rule,
the Security Rule, DoD 6025.18-R or DoD 8580.02-R if done by the Government.

Specific Use and Disclosure Provisions

        (a) Except as otherwise limited in this Clause, the Contractor may use Protected Health
Information for the proper management and administration of the Contractor or to carry out the
legal responsibilities of the Contractor.
                                                                                   N62645-11-R-0027

                                                                                        Page 84 of 93


        (b) Except as otherwise limited in this Clause, the Contractor may disclose Protected Health
Information for the proper management and administration of the Contractor, provided that
disclosures are required by law, or the Contractor obtains reasonable assurances from the person
to whom the information is disclosed that it will remain confidential and used or further disclosed
only as required by law or for the purpose for which it was disclosed to the person, and the person
notifies the Contractor of any instances of which it is aware in which the confidentiality of the
information has been breached.

       (c) Except as otherwise limited in this Clause, the Contractor may use Protected Health
Information to provide Data Aggregation services to the Government as permitted by 45 CFR
164.504(e)(2)(i)(B).

      (d) Contractor may use Protected Health Information to report violations of law to
appropriate Federal and State authorities, consistent with 45 CFR 164.502(j)(1).

Obligations of the Government

   Provisions for the Government to Inform the Contractor of Privacy Practices and
Restrictions

        (a) Upon request the Government shall provide the Contractor with the notice of privacy
practices that the Government produces in accordance with 45 CFR 164.520, as well as any
changes to such notice.

       (b) The Government shall provide the Contractor with any changes in, or revocation of,
permission by Individual to use or disclose Protected Health Information, if such changes affect the
Contractor's permitted or required uses and disclosures.

       (c) The Government shall notify the Contractor of any restriction to the use or disclosure of
Protected Health Information that the Government has agreed to in accordance with 45 CFR
164.522.


Permissible Requests by the Government


    The Government shall not request the Contractor to use or disclose Protected Health
Information in any manner that would not be permissible under the Privacy Rule, Security Rule, or
other statute if done by the Government, except for providing Data Aggregation services to the
Government and for management and administrative activities of the Contractor as otherwise
permitted by this clause.

Termination

       (a) Termination. A breach by the Contractor of this clause, may subject the Contractor to
termination under any applicable default or termination provision of this Contract.

       (b) Effect of Termination.
                                                                                    N62645-11-R-0027

                                                                                         Page 85 of 93


               (1) If this contract has records management requirements, the records subject to
the Clause should be handled in accordance with the records management requirements. If this
contract does not have records management requirements, the records should be handled in
accordance with paragraphs (2) and (3) below

                (2) If this contract does not have records management requirements, except as
provided in paragraph (3) of this section, upon termination of this Contract, for any reason, the
Contractor shall return or destroy all Protected Health Information received from the Government,
or created or received by the Contractor on behalf of the Government. This provision shall apply to
Protected Health Information that is in the possession of subcontractors or agents of the
Contractor. The Contractor shall retain no copies of the Protected Health Information.

                (3) If this contract does not have records management provisions and the
Contractor determines that returning or destroying the Protected Health Information is infeasible,
the Contractor shall provide to the Government notification of the conditions that make return or
destruction infeasible. Upon mutual agreement of the Government and the Contractor that return
or destruction of Protected Health Information is infeasible, the Contractor shall extend the
protections of this Contract to such Protected Health Information and limit further uses and
disclosures of such Protected Health Information to those purposes that make the return or
destruction infeasible, for so long as the Contractor maintains such Protected Health Information.

Miscellaneous

         (a) Regulatory References. A reference in this Clause to a section in DoD 6025.18-R, DoD
8580.02-R, Privacy Rule or Security Rule means the section as in effect or as amended, and for
which compliance is required. This includes amendments specified in the Health Information
Technology for Economic and Clinical Health (HITECH) Act, enacted as title XIII of division A and
title IV of division B of the American Recovery and Reinvestment Act of 2009 (ARRA). Subtitle D of
the HITECH Act addresses the privacy and security concerns associated with the electronic
transmission of health information.



       (b) Survival. The respective rights and obligations of Business Associate under the ``Effect
of Termination'' provision of this Clause shall survive the termination of this Contract.

       (c) Interpretation. Any ambiguity in this Clause shall be resolved in favor of a meaning that
permits the Government to comply with DoD 6025.18-R, DoD 8580.02-R, Privacy Rule or Security
Rule


References:

      Public Law 107-347, E-Government Act, December 2002; Title III, Federal Information
       Security Management Act.
      Public Law 100-235, Computer Security Act of 1987
                                                                                N62645-11-R-0027

                                                                                    Page 86 of 93

      National Institute for Standards and Technology Special Publication 800-70, Security
       Configuration Checklists Program for IT Products – Guidance for Checklist Users and
       Developers, May 2005
      CNSSI 4012, National Information Assurance Training Standard for Senior System
       Managers, June 2004
      CNSSI 4013, National Information Assurance Training Standard for System Administrators,
       March 2004
      CNSSI 4015, National Training Standard for System Certifiers, December 2000
      DoDD 8100.01, Global Information Grid (GIG) Overarching Policy, 19 September 2002
      DoDD 8500.01E, Information Assurance, 24 October 2002
      DoDI 5000.2, Operation of the Defense Acquisition System, 12 May 03
      DoDI 5200.1-R, Information Security Program, January 1997
      DoDI 8500.2, Information Assurance (IA) Implementation, 6 February 2003
      DoDI 8510.01, Department of Defense Information Assurance Certification and
       Accreditation Process (DIACAP), 28 November 2007
      DoD 8570.01-M, Information Assurance Workforce Improvement Program, 19 December
       2005
      CJCSI 3170.01F, Joint Capabilities Integration and Development System, 1 May 2007
      CJCSI 6211.02B, Defense Information System Network (DISN): Policy, Responsibilities and
       Processes, 30 Aug 06
      CJCSI 6212.01B, Interoperability and Supportability of National Security Systems, and
       Information Technology Systems, 8 May 2000
      CJCSM 3170.01C, Operation of the Joint Capabilities Integration and Development System, 1
       May 2007
      CJCSM 6510.01, Defense-in-Depth: Information Assurance (IA) and Computer Network
       Defense (CND), 8 March 2006
      DISA Enclave Security Technical Implementation Guide, Version 4, Release 2
      DON-CIO Memo 0-10, 26 Apr 2010 – Information Assurance Policy for Platform
       Information Technology
      TRICARE Systems Manual 7950.1-M
      SECNAV M-5239.1 Department of the Navy Information Assurance Program
      Department of the Navy DIACAP Handbook, Version 1.0
      DoD IPv6 Standard Profiles for IPv6 Capable Products – Supplemental Guidance v3.0.
      Federal Acquisition Regulation parts 7, 11, 12, and 39
      Defense Information Systems Agency (DISA) – http://www.disa.mil



REPAIR DEFINITIONS
                                       ATTACHMENT 4
REPAIR DEFINITIONS
                                                                      N62645-11-R-0027

                                                                           Page 87 of 93




                                              Service Level:
                                                 Remote            Service Level:
Severity Level           Definition             Solution           Field Solution

                 Hardware, software, or       System             System restored
                 procedural problem           restored on        on 99% of calls
Level 1
                 preventing site from         99% of calls       within 24hours
(Server
                 filling new prescriptions    within 4 hours     of the time the
and/or all
                 and causes system            of the time the    call is opened.
workstations
                 downtime. Entire             call is opened.
Down)
                 system is not-                                  OCONUS: 48
                 functioning.                                    hours

                 Hardware, software, or       System             System restored
                 procedural problem           restored on        on 98% of calls
                 prevents site from filling   95% of calls       within 24 hours
Level 2          new prescriptions and        within 5 hours     of the time the
(Robot Down)     causes system                of the time the    call is opened.
                 downtime.                    call is opened.
                                                                 OCONUS: 72
                                                                 hours

                 Hardware, software, or       90% of calls       90% of calls
                 procedural problem           resolved           resolved within
                 causing substantial          within 24          48 hours of the
                 operational difficulty,      hours of the       time the call is
Level 3
                 but not preventing a         time the call is   opened.
(Major)
                 system from filling new      opened.
                 prescriptions. System                           OCONUS: 192
                 performance degraded                            hours
                 but operational.

                 Hardware, software, or       90% of calls       90% of calls
                 procedural problem not       resolved           resolved within
                 causing substantial          within 36          48 hours of the
                 operational difficulty,      hours of the       time the call is
                 and also not preventing      time the call is   opened, or on the
                 a system from filling        opened.            next scheduled
Level 4          new prescriptions. This                         preventive
(Minor)          includes a training or                          maintenance
                 procedural problem not                          visit.
                 preventing the site from
                 conducting business.                            OCONUS: 192
                 This level is also used to                      hours
                 flag preventive
                 maintenance issues.
                                                                                      N62645-11-R-0027

                                                                                           Page 88 of 93




TABLE OF DELIVERABLES
                                           ATTACHMENT 5
           TABLE OF DELIVERABLES
           To be included with each delivery order

List of countable drugs
Project Management Plan to meet Sept 2012 deadline
5 Year Lifecycle Plan
Technical Specification Information for Components
Information related to explanation of Vendor Solution
Information on available Customer Technical Support (remote, telephone, onsite, hardware, software, database/system




PRICING CONFIGURATIONS
                                           ATTACHMENT 6

Pricing Configuration – Large Facility

       Shall provide a solution capable of dispensing 300 Rx/hr, taking into account throughput of both
        manual and robotic dispensing
       At least two Automatic Tablet Dispensing Counters shall be provided
             o Automatic Tablet Dispensing Counters shall be provided to accommodate 225 separate
                 medications
             o 75 medications shall be duplicated in each robotic medication dispensing system
                 provided
       Automated Tablet Dispensing Counter(s) shall be capable of a combined total throughput of at
        least 200 Rx/hr. Shall include two fast moving manual workstations
       Shall include two slow moving manual workstations
       Shall include five pharmacist verification workstations
       Shall include one workstation for C2-5 controlled substances and refrigerated medications.
       Conveyor system shall consist of 140 feet of track, no elevations
                                                                                           N62645-11-R-0027

                                                                                                  Page 89 of 93

       Shall include necessary servers/software licenses necessary to allow system to operate
       Vendor shall include installation pricing.
            o Though individual delivery orders shall likely require site renovations, for this pricing
                 purpose, vendor shall assume no site renovations will be required.
Pricing Configuration – Medium Facility

        Shall provide solution capable of dispensing 125 Rx/hr, taking into account throughput of both
         manual and robotic dispensing
        At least one Automatic Tablet Dispensing Counter shall be provided
              o Automatic Tablet Dispensing Counter(s) shall be provided to accommodate 100
                  separate medications
              o 25 medications shall be duplicated in each robotic medication dispensing system
                  provided, if more than one is provided
              o Automated Tablet Dispensing Counter(s) shall be capable of a combined total
                  throughput of at least 100 Rx/hr.
        Shall include one fast moving manual workstation
        Shall include two slow moving manual workstations
              o C2-5, controlled substances and refrigerated medications shall be dispensed from one
                  of the slow moving manual workstations
        Shall include four pharmacist verification workstations
        Conveyor system shall consist of 60 feet of track, no elevations
        Shall include necessary servers/software licenses necessary to allow system to operate
        Vendor shall include installation pricing.
              o Though individual delivery orders shall likely require site renovations, for this pricing
                  purpose, vendor shall assume no site renovations will be required.



MDS2 FORM
                                   ATTACHMENT 7
The information provided on the MDS2 form will be used to evaluate both subfactors.


   Manufacturer Disclosure Statement for Medical Device
                     Security – MDS²
   SECTION 1
Device Category                              Manufacturer                      Document ID                 Document Release Date


Device Model                                 Software Revision                Software Release Date

Manufacturer or          Company Name                                   Manufacturer Contact Information
Representative Contact
Information:
                         Representative Name/Position
                                                                                                                         N62645-11-R-0027

                                                                                                                               Page 90 of 93


MANAGEMENT OF ELECTRONIC PROTECTED HEALTH INFORMATION (ePHI)                                                                                    Yes No N/A Note #
 1. Can this device transmit or maintain electronic Protected Health Information                                                                 ______    _____
(ePHI)?..................................................................
 2. Types of ePHI data elements that can be maintained by the device:
    a. Demographic (e.g., name, address, location, unique identification                                                                         ______    _____
    number)?............................................................................
    b. Medical record (e.g., medical record #, account #, test or treatment date, device identification number)?.............................    ______    _____
    c. Diagnostic/therapeutic (e.g., photo/radiograph, test results, or physiologic data with identifying characteristics)?..............        ______    _____
    d. Open, unstructured text entered by device                                                                                                 ______    _____
    user/operator?..............................................................................................
    ..................
 3. Maintaining ePHI - Can the device
    a. Maintain ePHI temporarily in volatile memory (i.e., until cleared on by power-off or                                                      ______    _____
    reset)?......................................................
    b. Store ePHI persistently on local                                                                                                          ______    _____
    media?.......................................................................
    .......................................................................
    c. Import/export ePHI with other                                                                                                             ______    _____
    systems?....................................................................
    ...........................................................................
 4. Mechanisms used for the transmitting, importing/exporting of ePHI – Can the device
    a. Display ePHI (e.g., video                                                                                                                 ______    _____
    display)?.....................................................................
    ...................................................................................
    b. Generate hardcopy reports or images containing                                                                                            ______    _____
    ePHI?...........................................................................................................
    .......
    c. Retrieve ePHI from or record ePHI to removable media (e.g., disk, DVD, CD-ROM, tape, CF/SD card, memory stick)?.....                      ______    _____
    d. Transmit/receive or import/export ePHI via dedicated cable connection (e.g., IEEE 1073, serial port, USB, FireWire)?......                ______    _____
    e. Transmit/receive ePHI via a network connection (e.g., LAN, WAN, VPN, intranet,                                                            ______    _____
    Internet)?......................................................
    f. Transmit/receive ePHI via an integrated wireless connection (e.g. WiFi, Bluetooth,                                                        ______    _____
    infrared)?..................................................
    g. Other?                   ____________________________________________________........
                        .............................

ADMINISTRATIVE SAFEGUARDS                                                                                                                       Yes No N/A Note #
5.   Does manufacturer offer operator and technical support training or documentation on device security features?..................             ______    _____
6.   What underlying operating system(s) (including version number) are used by the device?          _____________.                              ______    _____
                                                                                                                 .........

PHYSICAL SAFEGUARDS                                                                                                                             Yes No N/A Note #
7.   Are all device components maintaining ePHI (other than removable media) physically secure (i.e. cannot remove without tools)?               ______    _____
8.   Does the device have an integral data backup capability (i.e., backup onto removable media like tape, disk)?.......................         ______    _____
9.   Can the device boot from uncontrolled or removable media (i.e., a source other than an internal drive or memory component)?                 ______    _____


TECHNICAL SAFEGUARDS                                                                                                                            Yes No N/A Note #
10. Can software or hardware not authorized by the device manufacturer be installed on the device without the use of tools?..                    ______    _____
11. Can the device be serviced remotely (i.e., maintenance activities performed by service person via network or remote connection)?             ______    _____
    a. Can the device restrict remote access to specific devices or network locations (e.g., specific IP addresses)?...................          ______    _____
    b. Can the device provide an audit trail of remote-service                                                                                   ______    _____
    activity?......................................................................................................
    c. Can security patches or other software be installed                                                                                       ______    _____
    remotely?.......................................................................................................
12. Level of owner/operator service access to device operating system: Can the device owner/operator
    a. Apply device manufacturer-validated security                                                                                              ______    _____
    patches?............................................................................................
    ........................
                                                                                                                      N62645-11-R-0027

                                                                                                                             Page 91 of 93

     b. Install or update antivirus                                                                                                          ______   _____
     software?........................................................
     ........................................................................
     ......................
     c. Update virus definitions on manufacturer-installed antivirus                                                                         ______   _____
     software?........................................................................................
     d. Obtain administrative privileges (e.g. access operating system or application via local root or admin account)?...............       ______   _____
 13. Does the device support user/operator specific username and                                                                             ______   _____
password?....................................................................................
 14. Does the system force reauthorization after a predetermined length of inactivity (e.g., auto logoff, session lock)?.................    ______   _____




 15. Events recorded in device audit trail (e.g., user, date/time, action taken): Can the audit trail
record.............................................
        a. Login and logout by                                                                                                               ______   _____
        users/operators?....................................................................
        ..............................................................................
        b. Viewing of                                                                                                                        ______   _____
        ePHI?............................
        .....................................
        .....................................
        .....................................
        .....................................
        .......
        c. Creation, modification or deletion of                                                                                             ______   _____
        ePHI?.........................................................................
        .................................................................
        d. Import/export or transmittal/receipt of                                                                                           ______   _____
        ePHI?.....................................................................................
        ...................................................
 16. Does the device incorporate an emergency access (“break-glass”) feature that is                                                         ______   _____
logged?.........................................................
 17. Can the device maintain ePHI during power service                                                                                       ______   _____
interruptions?....................................................................................................
 18. Controls when exchanging ePHI with other
devices:.....................................................................................................
.........................
        a. Transmitted only via a point-to-point dedicated                                                                                   ______   _____
        cable?.....................................................................................................................
        b. Encrypted prior to transmission via a network or removable                                                                        ______   _____
        media?.............................................................................................
        c. Restricted to a fixed list of network                                                                                             ______   _____
        destinations............................................................................
        .....................................................
 19. Does the device ensure the integrity of the ePHI data with implicit or explicit error detection/correction technology?...............   ______   _____




INSPECTION AND ACCEPTANCE TERMS

Supplies/services will be inspected/accepted at:

CLIN       INSPECT AT                                   INSPECT BY             ACCEPT AT                                     ACCEPT BY
0001       N/A                                          N/A                    N/A                                           Government
                                                                                                            N62645-11-R-0027

                                                                                                                Page 92 of 93

0002       Destination                                   Government             Destination                     Government
0003       Destination                                   Government             Destination                     Government
0004       Destination                                   Government             Destination                     Government
0005       Destination                                   Government             Destination                     Government


CLAUSES INCORPORATED BY FULL TEXT


SUP 5252.232-9402 INVOICING AND PAYMENT (WAWF) INSTRUCTIONS (April 2008)

(a) Invoices for goods received or services rendered under this contract shall be submitted electronically through
Wide Area Work Flow -- Receipt and Acceptance (WAWF):

          (1) The vendor shall have their cage code activated by calling 866-618-5988. Once activated, the vendor
shall self-register at the web site https://wawf.eb.mil. Vendor training is available on the Internet at
http://www.wawftraining.com. Additional support can be obtained by e-mailing BUMED WAWF support at
wawf@med.navy.mil.

          (2) WAWF Vendor “Quick Reference” Guides are located at the following web site:
http://acquisition.navy.mil/rda/home/acquisition_one_source/ebusiness/don_ebusiness_solutions/wawf_overview/ven
dor_information.

         (3) Select the invoice type within WAWF as specified below. Back up documentation (such as timesheets,
receiving reports etc.) can be included and attached to the invoice in WAWF. Attachments created in any Microsoft
Office product are attachable to the invoice in WAWF. Total limit for each file is not to exceed 2MB. Multiple
attachments are allowed.

(b) The following information regarding invoice routing DODAACs must be entered for completion of the invoice in
WAWF:
The following is an example of payment information that will be included on each delivery order:
                                                                                                   ROUTING TABLE
 WAWF Invoice Type (2-in-1, Combo, or Cost Voucher)
 Contract Number
 Delivery Order Number
 Issuing Office DoDAAC                                                                     N62645
 Admin Office DoDAAC                                                                       N62645
 Inspector DoDAAC (usually when Inspector & Acceptor are different                         N/A
 people)
 Ship To DoDAAC (for Combo), Service Acceptor DoDAAC (for 2-
 in-1), Service Approver DoDAAC (for Cost Voucher)
 Acceptance At Other DoDAAC                                                                N/A
 Local Processing Office (Certifier) DoDAAC
 DCAA Office DoDAAC (Used on Cost Voucher’s only)                                          N/A
 Paying Office DoDAAC                                                                      HQ0248
 Acceptor/COR Email Address
(c) Contractors approved by DCAA for direct billing will not process vouchers through DCAA, but may submit
directly to DFAS. Vendors MUST still provide a copy of the invoice and any applicable documentation that supports
payment to the Acceptor/Contracting Officer's Representative (COR) if applicable. Additionally, a copy of the
invoice(s) and attachment(s) at time of submission in WAWF must also be provided to each point of contact
identified in section (d) of this clause by email. If the invoice and/or receiving report are delivered in the email as an
attachment it must be provided as a .PDF, Microsoft Office product or other mutually agreed upon form between the
Contracting Officer and vendor.
                                                                                                 N62645-11-R-0027

                                                                                                       Page 93 of 93

(d) For each invoice / cost voucher submitted for payment, the contractor shall include the following email addresses
for the WAWF automated invoice notification to the following points of contact:
           NAME                                      EMAIL                         PHONE             ROLE
(Enter WAWF Acceptor POC info)                                                                    WAWF Acceptor

								
To top